Remote control and remote monitoring infrastructure for proton beam emitting and delivery system

ABSTRACT

A remote diagnostic monitoring and control of physical components of a particle accelerator system has a particle emitting system located at a first physical site and includes one or more particle emitting system components to operate the particle emitting system, a particle delivery system located at the first physical site and including one or more particle delivery system components to operate the particle delivery system, a particle system gateway located at the first physical site and operatively coupled to the particle emitting system components and the particle delivery system components by a first network interface, and a diagnostic monitoring system located at a second physical site remote from the first physical site, operatively coupled to the particle system gateway by a second network interface, and operable to monitor one or more first operating states corresponding to one or more of the particle emitting system components and one or more second operating states corresponding to one or more of the particle delivery system components, and a diagnostic control system located at the second physical site, operatively coupled to the particle system gateway by a third network interface, and operable to modify one or more of the first operating states of the one or more particle emitting system components and the second operating states the one or more particle delivery system components.

TECHNICAL FIELD

The present implementations relate generally to radiation therapy, andmore particularly to a remote control and remote monitoringinfrastructure for proton beam emitting and delivery systems.

BACKGROUND

Radiation therapy is becoming increasingly desired in the treatment ofmedical conditions and illnesses. Radiation therapy systems capable ofconcurrently treating multiple patients efficiently and effectively arealso becoming increasingly desired. Control and monitoring of radiationtherapy is thus becoming increasingly complex, and includes increasinglycomplex systems and devices in order to provide sufficient breadth oftreatment to sufficient number of patients at increasing aggregatevolume. Accordingly, maintaining operation of radiation therapy systemsis increasingly complex. Conventional radiation therapy systems requireincreasingly complex servicing and control of components of thosesystem. Such servicing of convention systems requires on-site servicingby technicians that can reduce system uptime and increase delay incritical medical care.

Conventional on-site servicing of proton beam therapy system requiressignificant monitoring and control service equipment co-located witheach proton beam therapy system. Each servicing center requires controland operation by technician staff, often requiring around-the-clockpresence of trained technician teams co-located with each deployedproton beam therapy system in order to ensure safe and reliableoperation. With the deployment of increasing numbers of proton beamtherapy systems across geographic boundaries, the high cost ofinstallation and operations of co-located service equipment increasessignificantly and requires significant numbers of technicians withinlimited geographical range of each proton beam therapy system deployed.Thus, cost and complexity of servicing proton beam therapy systems candramatically increase overall difficulty in deploying and operatingcritical medical treatments with proton beam therapy.

SUMMARY

To overcome the above and other issues, present implementations aredirected to infrastructure for remote monitoring and control of protonbeam emitting and delivery systems. Present implementations can reducethe number of co-located technicians and service monitoring and controlequipment required to perform monitoring and control of proton beamemitting and delivery systems, allowing proton beam emitting anddelivery systems to be deployed at significantly more locations whilereducing the infrastructure requirements and cost burdens associatedwith co-locating large staffs of technicians with at each proton beamemitting and delivery system location. Present implementations includemultiple hardware interconnects operatively couplable to specifichardware components of proton beam emitting and delivery systems. Theseinterconnects provide a technical solution for allowing servicingtechnicians to remotely monitor proton beam emitting and deliverysystems, and to diagnose operating faults without the requirement to beco-located with the proton beam emitting and delivery system location.Further, present implementations include a first dedicated communicationchannel for remote monitoring and a second dedicated communicationchannel for remote control of proton beam emitting and delivery systems,within network infrastructure operatively couplable to components ofproton beam emitting and delivery systems. Present implementationsfurther monitor and control operating states of one or more componentsof proton beam emitting and delivery systems directly, to conductservicing, troubleshooting, or the like. Thus, a technological solutionof an infrastructure for remote control and remote monitoring of protonbeam emitting and delivery systems is provided.

Example implementations include a system for remote diagnosticmonitoring and control of physical components of a particle acceleratorsystem, with a particle emitting system located at a first physical siteand including one or more particle emitting system components to operatethe particle emitting system, a particle delivery system located at thefirst physical site and including one or more particle delivery systemcomponents to operate the particle delivery system, a particle systemgateway located at the first physical site and operatively coupled tothe particle emitting system components and the particle delivery systemcomponents by a first network interface, and a diagnostic monitoringsystem located at a second physical site remote from the first physicalsite, operatively coupled to the particle system gateway by a secondnetwork interface, and operable to monitor one or more first operatingstates corresponding to one or more of the particle emitting systemcomponents and one or more second operating states corresponding to oneor more of the particle delivery system components, and a diagnosticcontrol system located at the second physical site, operatively coupledto the particle system gateway by a third network interface, andoperable to modify one or more of the first operating states of the oneor more particle emitting system components and the second operatingstates the one or more particle delivery system components.

Example implementations also include a system where the particle systemgateway further includes a component detector configured to perform acomponent detection operation to detect one or more of the particleemitting system components present at the particle emitting system andone or more of the particle delivery system components present at theparticle delivery system.

Example implementations also include a system where the componentdetector is further configured to perform the component detectionoperation during initialization of one or more of the particle systemgateway, the particle emitting system, and the particle delivery system.

Example implementations include a system where the component detector isfurther configured to perform the component detection operation byinterrogating one or more of the particle emitting system components andone or more of the particle delivery system components.

Example implementations also include a system where the particle systemgateway further includes an interlock processor configured to perform acomponent dependency operation to identify at least one particle systemdevice including at least one included particle system component, wherethe particle system component includes at least one of the particleemitting system components present at the particle emitting system, orat least one of the particle delivery system components present at theparticle delivery system.

Example implementations also include a system where the diagnosticcontrol system further includes an interlock controller configured toperform a component interlock operation to associate an interlockoperating state with the particle system device, the interlock statebased on a component operating state of the particle system componentand an interlock condition, where the component operating statecorresponds to at least one of the first operating states and the secondoperating states.

Example implementations also include a system where the interlockcondition includes an instruction to modify the device operating stateto correspond to the component operating state.

Example implementations also include a system where the device operatingstate and the component operating state include a fault state.

Example implementations also include a system further including a secondparticle delivery system located at the first physical site andincluding one or more second particle delivery system components tooperate the second particle delivery system independently of the firstparticle delivery system, where the particle system gateway is furtheroperatively coupled to the second particle delivery system components bythe first network interface.

Example implementations also include a system where the diagnosticmonitoring system is further operable to monitor one or more thirdoperating states corresponding to one or more of the second particleemitting system components, and the diagnostic control system is furtheroperable to modify one or more of the third operating states.

Example implementations also include a method for remote diagnosticmonitoring and control of physical components of a particle acceleratorsystem, by obtaining, by at least one processor at a second physicalsite, from a particle system gateway located at a first physical site, adetection of one or more particle emitting system components present ata particle emitting system located at the first physical site andincluding one or more of the particle emitting system components tooperate the particle emitting system, obtaining, by the at least oneprocessor, from the particle system gateway, a detection of one or moreparticle delivery system components present at a particle deliverysystem located at the first physical site and including one or more ofthe particle delivery system components to operate the particle deliverysystem, monitoring, by the at least one processor, one or more firstoperating states corresponding to one or more of the particle emittingsystem components and one or more second operating states correspondingto one or more of the particle delivery system components, andtransmitting, by the at least one processor, one or more of one or morefirst modified operating states based on one or more of the firstoperating states of the one or more particle emitting system components,and one or more second modified operating states based on one or more ofthe second operating states of the one or more particle delivery systemcomponents.

Example implementations also include a method of further identifying, bythe at least one processor, at least one particle system deviceincluding at least one included particle system component, where theparticle system component includes at least one of the particle emittingsystem components present at the particle emitting system, or at leastone of the particle delivery system components present at the particledelivery system.

Example implementations also include a method of further associating, bythe at least one processor, an interlock operating state with theparticle system device, where the interlock state is based on acomponent operating state of the particle system component and aninterlock condition, and the component operating state corresponds to atleast one of the first operating states and the second operating states.

Example implementations also include a method where the interlockcondition includes an instruction to modify the device operating stateto correspond to the component operating state.

Example implementations also include a method where the particle systemgateway is operatively coupled to the particle emitting systemcomponents and the particle delivery system components by a firstnetwork interface.

Example implementations also include a method where the diagnosticmonitoring system is located at a second physical site remote from thefirst physical site, and is operatively coupled to the particle systemgateway by a second network interface.

Example implementations also include a method where the diagnosticcontrol system is located at the second physical site, and isoperatively coupled to the particle system gateway by a third networkinterface.

Example implementations also include a method for remote diagnosticmonitoring and control of physical components of a particle acceleratorsystem, by detecting, by a particle system gateway located at a firstphysical site, one or more particle emitting system components presentat a particle emitting system located at the first physical site andincluding one or more of the particle emitting system components tooperate the particle emitting system, detecting, from the particlesystem gateway, one or more particle delivery system components presentat a particle delivery system located at the first physical site andincluding one or more of the particle delivery system components tooperate the particle delivery system, transmitting, to a diagnosticmonitoring system located at a second physical site remote from thefirst physical site, one or more first operating states corresponding toone or more of the particle emitting system components and one or moresecond operating states corresponding to one or more of the particledelivery system components, and receiving, from a diagnostic controlsystem located at the second physical site, one or more of firstmodified operating states of the one or more particle emitting systemcomponents and second modified operating states of the one or moreparticle delivery system components.

Example implementations also include a method of further initializingone or more of the particle system gateway, the particle emittingsystem, and the particle delivery system, where the detecting theparticle emitting system components includes detecting the particleemitting system components present at the particle emitting system, inresponse to the initializing, and the detecting the particle deliverysystem components includes detecting the particle delivery systemcomponents present at the particle delivery system, in response to theinitializing.

Example implementations also include a method of further interrogatingone or more of the particle emitting system components and one or moreof the particle delivery system components.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other aspects and features of the present implementations willbecome apparent to those ordinarily skilled in the art upon review ofthe following description of specific implementations in conjunctionwith the accompanying figures, wherein:

FIG. 1 illustrates a system for remote control and remote monitoring ofa proton beam emitting and delivery system, according to an embodiment.

FIG. 2 illustrates a proton beam system gateway, further to the systemof FIG. 1, according to an embodiment.

FIG. 3 illustrates a proton beam delivery component interface, furtherto the proton beam system gateway of FIG. 2, according to an embodiment.

FIG. 4 illustrates a proton beam emitting component interface, furtherto the proton beam system gateway of FIG. 2, according to an embodiment.

FIG. 5 illustrates a system memory, further to the proton beam systemgateway of FIG. 2, according to an embodiment.

FIG. 6 illustrates a diagnostic system, further to the system of FIG. 1,according to an embodiment.

FIG. 7 illustrates a system memory further to the diagnostic system ofFIG. 6, according to an embodiment.

FIG. 8 illustrates a graphical user interface for remote monitoring of aproton beam emitting and delivery system, according to an embodiment.

FIG. 9 illustrates a graphical user interface for remote monitoring of aproton beam emitting and delivery system including a hierarchicalpresentation, according to an embodiment.

FIG. 10 illustrates a graphical user interface for remote control andremote monitoring of a proton beam emitting and delivery systemincluding an interlock schematic presentation, according to anembodiment.

FIG. 11 illustrates a graphical user interface for remote control andremote monitoring of a proton beam emitting and delivery systemincluding an interlock schematic presentation and a component schematicpresentation, according to an embodiment.

FIG. 12 illustrates a method of remote monitoring of a proton beamemitting and delivery system, according to an embodiment.

FIG. 13 illustrates a method of remote monitoring of a proton beamemitting and delivery system further to the method of FIG. 12, accordingto an embodiment.

FIG. 14 illustrates a remote monitoring of a proton beam emitting anddelivery system further to the method of FIG. 13, according to anembodiment.

FIG. 15 illustrates a method of remote control of a proton beam emittingand delivery system, according to an embodiment.

FIG. 16 illustrates a method of remote control of a proton beam emittingand delivery system further to the method of FIG. 15, according to anembodiment.

FIG. 17 illustrates a method of remote control of a proton beam emittingand delivery system at a service location, according to an embodiment.

FIG. 18 illustrates a method of remote control of a proton beam emittingand delivery system at a service location, further to the method of FIG.17, according to an embodiment.

FIG. 19 illustrates a method of remote control of a proton beam emittingand delivery system at a clinical location, according to an embodiment.

FIG. 20 illustrates a method of remote control of a proton beam emittingand delivery system at a clinical location, further to the method ofFIG. 19, according to an embodiment.

DETAILED DESCRIPTION

The present implementations will now be described in detail withreference to the drawings, which are provided as illustrative examplesof the implementations so as to enable those skilled in the art topractice the implementations and alternatives apparent to those skilledin the art. Notably, the figures and examples below are not meant tolimit the scope of the present implementations to a singleimplementation, but other implementations are possible by way ofinterchange of some or all of the described or illustrated elements.Moreover, where certain elements of the present implementations can bepartially or fully implemented using known components, only thoseportions of such known components that are necessary for anunderstanding of the present implementations will be described, anddetailed descriptions of other portions of such known components will beomitted so as not to obscure the present implementations.Implementations described as being implemented in software should not belimited thereto, but can include implementations implemented inhardware, or combinations of software and hardware, and vice-versa, aswill be apparent to those skilled in the art, unless otherwise specifiedherein. In the present specification, an implementation showing asingular component should not be considered limiting; rather, thepresent disclosure is intended to encompass other implementationsincluding a plurality of the same component, and vice-versa, unlessexplicitly stated otherwise herein. Moreover, applicants do not intendfor any term in the specification or claims to be ascribed an uncommonor special meaning unless explicitly set forth as such. Further, thepresent implementations encompass present and future known equivalentsto the known components referred to herein by way of illustration.

Present implementations are directed variously to hardwareinterconnects, network infrastructure, and user interfaces for providinga technical solution of an infrastructure for remote monitoring andcontrol of proton beam emitting and delivery systems. First, presentimplementations include hardware interconnects operatively couplable tospecific hardware components of proton beam emitting and deliverysystems to monitor the operating state of those hardware components.Thus, implementations in accordance with present implementations canprovide direct hardware-level monitoring and control of components ofproton beam emitting and delivery systems, and reduce and eliminate theneed of costly co-located technician teams and service equipment. Asingle diagnostic system can be coupled to an arbitrary number of protonbeam emitting and delivery systems at a remote location by a dedicatedservice communication channel. The service communication channel can beInternet-enabled to allow direct hardware-level monitoring and controlof components of proton beam emitting and delivery systems from anylocation. Thus, present implementations can enable a technologicalsolution of direct and secure remote monitoring and control of protonbeam emitting and delivery system hardware components.

FIG. 1 illustrates an example system for remote control and remotemonitoring of a proton beam emitting and delivery system, in accordancewith present implementations. As illustrated by way of example in FIG.1, an example system 100 includes a diagnostic system 600 at a servicelocation 110, and a proton beam emitting system 130, a first proton beamdelivery system 140, a second proton beam delivery system 142, a protonbeam system gateway 200, a service communication channel 150, anoperation communication channel 152, and a control authorization toggleswitch 160 at a clinical location 120, a service control channel 102,and a service monitor channel 104.

The service location 110 includes a physical location including atechnician site. The service location 110 may correspond to an office,workstation, building, call center, or the like, and includes one ormore accommodations for one or more individuals to interact with adiagnostic system. The service location 110 can be located in aparticular geographic location, geographic region, geographicjurisdiction, or the like. As one example, a geographic jurisdiction canbe a particular city, state town, county, township, country, territory,continent, planetary hemisphere, or the like.

The diagnostic system 600 includes at least one electronic systemlocated at least partially at or within the service location 110, and isoperable to receive and transmit one or more instructions from and tothe clinical location 120. The diagnostic system 600 may be operativelycoupled to the proton beam gateway system 200 by one or more of theservice control channel 102 and the service monitor channel 104.

The clinical location 120 includes a physical location including aclinician site. The clinical location 120 may correspond to an office,workstation, building, clinic, hospital, operating room, emergency room,research facility, or the like, and includes one or more accommodationsfor one or more individuals to interact with the proton beam emittingsystem 130 and one or more of the proton beam delivery system 140 and142. The clinical location 120 can be located in a particular geographiclocation, geographic region, geographic jurisdiction, or the like. Asone example, a geographic jurisdiction can be a particular city, statetown, county, township, country, territory, continent, planetaryhemisphere, or the like. The clinical location 120 can be located at aphysical location remote from the service location 110. A first physicallocation can be remote from a second physical location where the firstphysical location and the second physical location are located atseparate places of corresponding type. As one example, the firstphysical location can be remotely located from the second physicallocation where the first physical location is a first building and thesecond physical location is a second building. In this example, thefirst and second physical locations can both be located in differentbuildings within the same or different jurisdictions, states, countries,hemispheres, or the like. As another example, the first physicallocation can be remotely located from the second physical location wherethe first physical location is a first city, town, or the like, and thesecond physical location is a second city, town, or the like. In thisexample, the first and second physical locations can both be located indifferent cities, town, or the like within the same or differentjurisdictions, states, countries, hemispheres, or the like.

The proton beam emitting system 130 includes a radiation generatingsystem operable to generate directed energy. The proton beam emittingsystem 130 can be or can include a cyclotron operable to generate one ormore focused energy beams including one or more proton beams or thelike. The proton beam emitting system 130 can generate at least oneproton beam having at least one distribution pattern corresponding toone or more operating states of one or more components thereof orassociated therewith. The proton beam emitting system 130 can beoperatively coupled to one or more proton beam delivery systems toprovide one or more proton beams to the proton beam delivery systems.The proton beam emitting system 130 can be operatively coupled to one ormore of the first proton beam delivery system 140 and the second protonbeam delivery system 142 by a beam transport system for transmitting aproton beam generated at the proton beam emitting system 130. The protonbeam emitting system 130 can be operatively coupled to one or more ofthe first proton beam delivery system 140 and the second proton beamdelivery system 142 by operation communication channel 152 fortransmitting instructions to operate the proton beam emitting system 130in accordance with at least one clinical therapy, proton beam therapy,radiation therapy, or the like.

The first proton beam delivery system 140 is or includes a radiationoutput system operable to apply directed energy to a target. A targetmay include a biological organism. As one example, a biological organismcan be a person, animal, or the like. As another example, a person canbe a patient undergoing a radiation therapy treatment in accordance withdirected energy applied from the first proton beam delivery system 140to at least a portion of a body, body part, or the like, of the patient.The first proton beam delivery system 140 may apply at least one protonbeam having at least one distribution pattern corresponding to one ormore operating states of one or more components thereof or associatedtherewith. The first proton beam delivery system 140 may include,correspond to, or be associated with, or the like, a patient treatmentroom of a medical facility at the clinical location 120. The patienttreatment room of the medical facility can correspond to a room, aradiology facility, or the like, of a hospital, medical facility,clinic, or the like.

The first proton beam delivery system 140 may be or may include one ormore moveable, articulable, or like components thereof or associatedtherewith. The first proton beam delivery system 140 can include atleast one nozzle including a beam output component. As one example, thenozzle can be a scanning nozzle operable to have a first outputcharacteristic corresponding to a first output aperture for directing aproton beam. As another example, the first output aperture cancorrespond to a proton beam shape having a size, energy, current, andthe like compatible with nondestructive application of a proton beam toliving tissue of a biological organism, patient, and the like. Asanother example, the nozzle can be an eye nozzle operable to have asecond output characteristic corresponding to a second output aperturefor directing a proton beam. As another example, the second outputaperture can correspond to a proton beam shape having a size, energy,current, and the like compatible with nondestructive application of aproton beam to living ocular tissue of a biological organism, patient,and the like.

The second proton beam delivery system 142 includes a radiation outputsystem operable to apply directed energy to a target independently of,concurrently, with, or the like, the first proton beam delivery system140. The second proton beam delivery system 142 can correspond in one ormore of structure and operation to the first proton beam delivery system140. The second proton beam delivery system 142 may include, correspondto, or be associated with, or the like, a patient treatment room of amedical facility at the clinical location 120 and separate from acorresponding patient treatment room of the first proton beam deliverysystem 140. The clinical location 120 can include an arbitrary number ofproton beam delivery systems, and is not limited to the first protonbeam delivery system 140 and the second proton beam delivery system 142.Proton beam emitting system 130 can be operatively coupled to anarbitrary number of proton beam delivery systems, and is not limited tobeing operatively coupled to the first proton beam delivery system 140and the second proton beam delivery system 142.

The service communication channel 150 is operable to operatively coupleone or more of the proton beam emitting system 130, the first protonbeam delivery system 140, and the second proton beam delivery system 142to the proton beam system gateway 200. The service communication channel150 may be operable to receive and transmit one or more instructions forcontrol and monitoring of the proton beam emitting system 130, the firstproton beam delivery system 140, and the second proton beam deliverysystem 142. The service communication channel 150 may be include one ormore digital, analog, or like communication channels, lines, traces, orthe like. As one example, the service communication channel 150 is orincludes at least one serial or parallel communication line amongmultiple communication lines of a communication interface. The servicecommunication channel 150 may be or include one or more wirelesscommunication devices, systems, protocols, interfaces, or the like. Theservice communication channel 150 may include one or more logical orelectronic devices including but not limited to integrated circuits,logic gates, flip flops, gate arrays, programmable gate arrays, and thelike. The service communication channel 150 may include ones or moretelecommunication devices including but not limited to antennas,transceivers, packetizers, wired interface ports, and the like.

The operation communication channel 152 is operable to operativelycouple one or more of the proton beam emitting system 130, the firstproton beam delivery system 140, and the second proton beam deliverysystem 142 to a distinct proton beam therapy control system 170. Theproton beam therapy control system 170 can be located at least partiallyat the clinical location 120, can be located at least partially at anylocation remote from the clinical location, or any combination thereof.The operation communication channel 152 may be operable to receive andtransmit one or more instructions for operation of the proton beamemitting system 130, the first proton beam delivery system 140, and thesecond proton beam delivery system 142 in accordance with one or moreclinical therapies, treatments, or the like including application of aproton beam, radiation, or the like. The operation communication channel152 may correspond in one or more of structure and operation to theservice communication channel 150.

The proton beam system gateway 200 includes one or more communicationinterfaces to operatively couple one or more of the proton beam emittingsystem 130, the first proton beam delivery system 140, and the secondproton beam delivery system 142 to the diagnostic system 600 by one ormore of the service control channel 102 and the service monitor channel104. The proton beam system gateway 200 may be operable to route,mediate, select, switch, or the like, instructions between thediagnostic system 600 and one or more components of the proton beamemitting system 130, the first proton beam delivery system 140, and thesecond proton beam delivery system 142.

The proton beam system gateway 200 can advantageously interface with thecomponents of one or more of the proton beam emitting system 130, thefirst proton beam delivery system 140, and the second proton beamdelivery system 142 directly, thereby reducing and eliminating failurepoints in remote service control and remote service monitoring of thosesystems at the clinical location 120. Thus, the proton beam systemgateway 200 can directly receive one or more operating states fromcomponents of the proton beam emitting system 130, the first proton beamdelivery system 140, and the second proton beam delivery system 142 by aphysical, hardware, logical, or like connection thereto. Further, theproton beam system gateway 200 can bypass high-level operating systems,personally identifiable information (PII), personal health information(PHI), and the like, by separating the control and monitoring operationsof the proton beam system gateway 200 from clinical operations,therapeutic operations, treatment operations, and the like.

The control authorization toggle switch 160 includes a physical controlaffordance operable to indicate that the diagnostic system 600 isauthorized to execute a control instruction at one or more components ofone or more of the proton beam emitting system 130, the first protonbeam delivery system 140, and the second proton beam delivery system142. The control authorization toggle switch 160 may include a buttonthat can be pressed to send an authorization instruction to the protonbeam system gateway 200. The control authorization toggle switch 160 mayinclude one or more visual indicators operable to indicate a controlauthorization state, prompt, or the. As one example, the controlauthorization toggle switch 160 can include a green LED, light, or thelike disposed within around, proximate to, or the like, the controlauthorization toggle switch 160, that can indicate that the controlauthorization toggle switch 160 indicates that the proton beam systemgateway 200 is authorized to transmit one or more control instructions.As another example, the control authorization toggle switch 160 caninclude a red LED, light, or the like disposed within around, proximateto, or the like, the control authorization toggle switch 160, that canindicate that the control authorization toggle switch 160 indicates thatthe proton beam system gateway 200 is authorized to transmit one or morecontrol instructions. As another example, the control authorizationtoggle switch 160 can include a pulsating, dimming, brightening, fading,or the like, LED, light, or the like disposed within around, proximateto, or the like, the control authorization toggle switch 160, that canindicate the control authorization toggle switch 160 indicates that theproton beam system gateway 200 is requesting one or more controlauthorization instructions. The control authorization toggle switch 160may be stateless and may provide an activation response independent ofone or more of a present, previous, or future physical orientation ofthe control authorization toggle switch 160.

The service control channel 102 is operable to operatively couple theproton beam system gateway 200 to the diagnostic system 600 to transmitone or more instructions therebetween for controlling one or more of theproton beam emitting system 130, the first proton beam delivery system140, and the second proton beam delivery system 142. The service controlchannel 102 can advantageously couple the proton beam system gateway 200to the diagnostic system 600 by a dedicated physical communicationchannel, logical communication channel, or the like. Thus, the servicecontrol channel 102 may be operable to provide secure, dedicated, andstable control communication from a service location 110 to a clinicallocation 120 for control communications substantially free ofinterference from monitoring communications. Further, the servicecontrol channel 102 may be operable to provide secure, dedicated, andstable control communication from a service location 110 to componentsof one or more of the proton beam emitting system 130, the first protonbeam delivery system 140, and the second proton beam delivery system 142at a clinical location 120.

The service control channel 102 may include one or more digital, analog,or like communication channels, lines, traces, or the like. As oneexample, the service control channel 102 is or includes at least oneserial or parallel communication line among multiple communication linesof a communication interface. The service control channel 102 may be ormay include one or more wireless communication devices, systems,protocols, interfaces, or the like. The service control channel 102 mayinclude one or more logical or electronic devices including but notlimited to integrated circuits, logic gates, flip flops, gate arrays,programmable gate arrays, and the like. The service control channel 102may include ones or more telecommunication devices including but notlimited to antennas, transceivers, packetizers, wired interface ports,and the like.

The service monitor channel 104 is operable to operatively couple theproton beam system gateway 200 to the diagnostic system 600 to transmitone or more instructions therebetween for monitoring one or more of theproton beam emitting system 130, the first proton beam delivery system140, and the second proton beam delivery system 142. The service monitorchannel 104 can advantageously couple the proton beam system gateway 200to the diagnostic system 600 by a dedicated physical communicationchannel, logical communication channel, or the like. Thus, the servicemonitor channel 104 may be operable to provide secure, dedicated, andstable control communication from a service location 110 to a clinicallocation 120 for monitoring communications substantially free ofinterference from control communications. Further, the service monitorchannel 104 may be operable to provide secure, dedicated, and stablecontrol communication from a service location 110 to components of oneor more of the proton beam emitting system 130, the first proton beamdelivery system 140, and the second proton beam delivery system 142 at aclinical location 120. The service monitor channel 104 can correspond inone or more of structure and operation to the service control channel102.

FIG. 2 illustrates an example proton beam system gateway, further to theexample system of FIG. 1. As illustrated by way of example in FIG. 2, anexample proton beam system gateway 200 includes a system processor 210,a system memory 500, a system control communication interface 220, asystem monitor communication interface 230, a first proton beam deliverycomponent interface 300, a second proton beam delivery componentinterface 302, and a proton beam emitting component interface 400.

The system processor 210 is operable to execute one or more instructionsassociated with input from the diagnostic system 600. The systemprocessor 210 may be an electronic processor, an integrated circuit, orthe like including one or more of digital logic, analog logic, digitalsensors, analog sensors, communication buses, volatile memory,nonvolatile memory, and the like. The system processor 210 may includebut is not limited to, at least one microcontroller unit (MCU),microprocessor unit (MPU), central processing unit (CPU), graphicsprocessing unit (GPU), physics processing unit (PPU), embeddedcontroller (EC), or the like. The system processor 210 may include amemory operable to store or storing one or more instructions foroperating components of the system processor 210 and operatingcomponents operably coupled to the system processor 210. The one or moreinstructions may include at least one of firmware, software, hardware,operating systems, embedded operating systems, and the like. The systemprocessor 210 or the proton beam system gateway 200 generally caninclude at least one communication bus controller to effectcommunication between the system processor 210 and the other elements ofthe proton beam system gateway 200. The system processor 210 includes afirst component interface channel 240, a second component interfacechannel 242, and a third component interface channel 400. The first,second, and third component interface channels 240, 242 and 250 areoperable to operatively couple the system processor 210 respectively tothe first proton beam delivery component interface 300, the secondproton beam delivery component interface 302, and the proton beamemitting component interface 400. One or more of the first, second, andthird component interface channels 240, 242 and 250 can be integratedinto a combined, single, or like channel.

The system memory 500 is operable to store data associated with theproton beam system gateway 200. The system memory 500 may include onesor more hardware memory devices for storing binary data, digital data,or the like. The system memory 500 may include one or more electricalcomponents, electronic components, programmable electronic components,reprogrammable electronic components, integrated circuits, semiconductordevices, flip flops, arithmetic units, or the like. The system memory500 may include at least one of a non-volatile memory device, asolid-state memory device, a flash memory device, and a NAND memorydevice. The system memory 500 may include one or more addressable memoryregions disposed on one or more physical memory arrays. A physicalmemory array may include a NAND gate array disposed on a particularsemiconductor device, integrated circuit device, printed circuit boarddevice, and the like.

The system control communication interface 220 is operable to receiveand transmit one or more instructions by the service control channel 102to the diagnostic system 600. The system control communication interface220 may include a command translation unit operable to convert one ormore instructions between a processor format compatible with the systemprocessor 210 and a communication format compatible with one or more ofthe service control channel 102 and the diagnostic system 600. Thesystem control communication interface 220 may include one or morelogical or electronic devices including but not limited to integratedcircuits, logic gates, flip flops, gate arrays, programmable gatearrays, and the like. Any electrical, electronic, or like devices, orcomponents associated with the system control communication interface220 can also be associated with, integrated with, integrable with,replaced by, supplemented by, complemented by, or the like, the systemprocessor 210 or any component thereof.

The system monitor communication interface 230 is operable to receiveand transmit one or more instructions by the service monitor channel 104to the diagnostic system 600. The system monitor communication interface230 may include a command translation unit operable to convert one ormore instructions between a processor format compatible with the systemprocessor 210 and a communication format compatible with one or more ofthe service monitor channel 104 and the diagnostic system 600. Thesystem monitor communication interface 230 may include one or morelogical or electronic devices including but not limited to integratedcircuits, logic gates, flip flops, gate arrays, programmable gatearrays, and the like. Any electrical, electronic, or like devices, orcomponents associated with the system monitor communication interface230 can also be associated with, integrated with, integrable with,replaced by, supplemented by, complemented by, or the like, the systemprocessor 210 or any component thereof.

The first proton beam delivery component interface 300 is operable toreceive and transmit one or more instructions by a first proton beamsystem communication channel 260 of the service communication channel150 to the first proton beam delivery system 140. The first proton beamdelivery component interface 300 may include a command translation unitoperable to convert one or more instructions between a processor formatcompatible with the system processor 210 and a communication formatcompatible with one or more of the first proton beam systemcommunication channel 260 and the first proton beam delivery system 140.The first proton beam delivery component interface 300 may include oneor more logical or electronic devices including but not limited tointegrated circuits, logic gates, flip flops, gate arrays, programmablegate arrays, and the like. Any electrical, electronic, or like devices,or components associated with the first proton beam delivery componentinterface 300 can also be associated with, integrated with, integrablewith, replaced by, supplemented by, complemented by, or the like, thesystem processor 210 or any component thereof.

The second proton beam delivery component interface 302 is operable toreceive and transmit one or more instructions by a second proton beamsystem communication channel 262 of the service communication channel150 to the second proton beam delivery system 142. The second protonbeam delivery component interface 302 may include a command translationunit operable to convert one or more instructions between a processorformat compatible with the system processor 210 and a communicationformat compatible with one or more of the second proton beam deliverycomponent interface 302 and the second proton beam delivery system 142.The second proton beam delivery component interface 302 may include oneor more logical or electronic devices including but not limited tointegrated circuits, logic gates, flip flops, gate arrays, programmablegate arrays, and the like. Any electrical, electronic, or like devices,or components associated with the second proton beam delivery componentinterface 302 can also be associated with, integrated with, integrablewith, replaced by, supplemented by, complemented by, or the like, thesystem processor 210 or any component thereof.

The proton beam emitting component interface 400 is operable to receiveand transmit one or more instructions by a third proton beam systemcommunication channel 270 of the service communication channel 150 tothe proton beam emitting system 130. The proton beam emitting componentinterface 400 may include a command translation unit operable to convertone or more instructions between a processor format compatible with thesystem processor 210 and a communication format compatible with one ormore of the proton beam emitting component interface 400 and the protonbeam emitting system 130. The proton beam emitting component interface400 may include one or more logical or electronic devices including butnot limited to integrated circuits, logic gates, flip flops, gatearrays, programmable gate arrays, and the like. Any electrical,electronic, or like devices, or components associated with the protonbeam emitting component interface 400 can also be associated with,integrated with, integrable with, replaced by, supplemented by,complemented by, or the like, the system processor 210 or any componentthereof.

FIG. 3 illustrates an example proton beam delivery component interface,further to the example proton beam system gateway of FIG. 2. Asillustrated by way of example in FIG. 3, an example proton beam deliverycomponent interface 300 includes at least one scanning nozzleinterconnect 310, at least one eye nozzle interconnect 320, at least onetable actuator interconnect 330, at least one gantry actuatorinterconnect 340, at least one chair actuator interconnect 350, at leastone proton beam positioner interconnect 360, at least one proton beamenergy interconnect 370, at least one patient positioner interconnect380, and at least one imager interconnect 390. The proton beam deliverycomponent interface 302 can correspond in one or more of structure andoperation to the proton beam delivery component interface 300.

The scanning nozzle interconnect 310 is operable to operatively couplean electrical, electronic, or like component of a scanning nozzle of theproton beam delivery system 140 or 142 respectively to the componentinterface channel 240 or 242. The scanning nozzle interconnect 310 mayinclude one or more physical control contacts 312 coupled to, integratedwith, detachably attached to, or the like, a scanning nozzle of theproton beam delivery system 140 or 142. As one example, the controlcontacts 312 of the scanning nozzle interconnect 310 can operativelycouple the scanning nozzle interconnect 310 to one or more of a powerswitch, a power reset switch, one or more scanning nozzle positioningmotors, one or more scanning nozzle aperture motors, and the like. Thescanning nozzle interconnect 310 may include one or more physicalmonitoring contacts coupled to, integrated with, detachably attached to,or the like, the scanning nozzle of the proton beam delivery system 140or 142. As one example, the control contacts 312 of the scanning nozzleinterconnect 310 can operatively couple the scanning nozzle interconnect310 to one or more of a component voltage sensor, a component currentsensor, one or more scanning nozzle position sensors, one or morescanning nozzle aperture sensors, and the like. The scanning nozzleinterconnect 310 may include one or more logical or electronic devicesincluding but not limited to jumper contacts, solder contacts,integrated circuits, logic gates, flip flops, gate arrays, programmablegate arrays, and the like.

The eye nozzle interconnect 320 is operable to operatively couple anelectrical, electronic, or like component of an eye nozzle of the protonbeam delivery system 140 or 142 respectively to the component interfacechannel 240 or 242. The eye nozzle interconnect 320 may include one ormore physical control contacts 322 coupled to, integrated with,detachably attached to, or the like, an eye nozzle of the proton beamdelivery system 140 or 142. As one example, the control contacts 322 ofthe eye nozzle interconnect 320 can operatively couple the eye nozzleinterconnect 320 to one or more of a power switch, a power reset switch,one or more eye nozzle positioning motors, one or more eye nozzleaperture motors, and the like. The eye nozzle interconnect 320 mayinclude one or more physical monitoring contacts coupled to, integratedwith, detachably attached to, or the like, the eye nozzle of the protonbeam delivery system 140 or 142. As one example, the control contacts322 of the eye nozzle interconnect 320 can operatively couple the eyenozzle interconnect 320 to one or more of a component voltage sensor, acomponent current sensor, one or more eye nozzle position sensors, oneor more eye nozzle aperture sensors, and the like. The eye nozzleinterconnect 320 may include one or more logical or electronic devicesincluding but not limited to jumper contacts, solder contacts,integrated circuits, logic gates, flip flops, gate arrays, programmablegate arrays, and the like.

The table actuator interconnect 330 is operable to operatively couple anelectrical, electronic, or like component of at least one table actuatorof the proton beam delivery system 140 or 142 respectively to thecomponent interface channel 240 or 242. The table actuator interconnect330 may include one or more physical control contacts 332 coupled to,integrated with, detachably attached to, or the like, at least onemotorized actuator of the proton beam delivery system 140 or 142. As oneexample, the control contacts 332 of the table actuator interconnect 330can operatively couple the table actuator interconnect 330 to one ormore of a power switch, a power reset switch, one or more patient tablepositioning motors, one or more patient table rotational motors, and thelike. The table actuator interconnect 330 may include one or morephysical monitoring contacts coupled to, integrated with, detachablyattached to, or the like, the patient table of the proton beam deliverysystem 140 or 142. As one example, the control contacts 332 of the tableactuator interconnect 330 can operatively couple the table actuatorinterconnect 330 to one or more of a component voltage sensor, acomponent current sensor, one or more table position sensors, one ormore table angle sensors, and the like. The table actuator interconnect330 may include one or more logical or electronic devices including butnot limited to jumper contacts, solder contacts, integrated circuits,logic gates, flip flops, gate arrays, programmable gate arrays, and thelike.

The gantry actuator interconnect 340 is operable to operatively couplean electrical, electronic, or like component of at least one gantryactuator of the proton beam delivery system 140 or 142 respectively tothe component interface channel 240 or 242. The gantry actuatorinterconnect 340 may include one or more physical control contacts 342coupled to, integrated with, detachably attached to, or the like, atleast one motorized actuator of the proton beam delivery system 140 or142. As one example, the control contacts 342 of the gantry actuatorinterconnect 340 can operatively couple the gantry actuator interconnect340 to one or more of a power switch, a power reset switch, one or morepatient gantry positioning motors, one or more patient gantry rotationalmotors, and the like. The gantry actuator interconnect 340 may includeone or more physical monitoring contacts coupled to, integrated with,detachably attached to, or the like, the patient gantry of the protonbeam delivery system 140 or 142. As one example, the control contacts342 of the gantry actuator interconnect 340 can operatively couple thegantry actuator interconnect 340 to one or more of a component voltagesensor, a component current sensor, one or more gantry position sensors,one or more gantry angle sensors, and the like. The gantry actuatorinterconnect 340 may include one or more logical or electronic devicesincluding but not limited to jumper contacts, solder contacts,integrated circuits, logic gates, flip flops, gate arrays, programmablegate arrays, and the like.

The chair actuator interconnect 350 is operable to operatively couple anelectrical, electronic, or like component of at least one chair actuatorof the proton beam delivery system 140 or 142 respectively to thecomponent interface channel 240 or 242. The chair actuator interconnect350 may include one or more physical control contacts 352 coupled to,integrated with, detachably attached to, or the like, at least onemotorized actuator of the proton beam delivery system 140 or 142. As oneexample, the control contacts 352 of the chair actuator interconnect 350can operatively couple the chair actuator interconnect 350 to one ormore of a power switch, a power reset switch, one or more patient chairpositioning motors, one or more patient chair rotational motors, and thelike. The chair actuator interconnect 350 may include one or morephysical monitoring contacts coupled to, integrated with, detachablyattached to, or the like, the patient chair of the proton beam deliverysystem 140 or 142. As one example, the control contacts 352 of chairactuator interconnect 350 can operatively couple the chair actuatorinterconnect 350 to one or more of a component voltage sensor, acomponent current sensor, one or more chair position sensors, one ormore chair angle sensors, and the like. The chair actuator interconnect350 may include one or more logical or electronic devices including butnot limited to jumper contacts, solder contacts, integrated circuits,logic gates, flip flops, gate arrays, programmable gate arrays, and thelike.

The proton beam positioner interconnect 360 is operable to operativelycouple an electrical, electronic, or like component of at least oneproton beam actuator of the proton beam delivery system 140 or 142respectively to the component interface channel 240 or 242. The protonbeam positioner interconnect 360 may include one or more physicalcontrol contacts 362 coupled to, integrated with, detachably attachedto, or the like, at least one motorized actuator of the proton beamdelivery system 140 or 142. As one example, the control contacts 362 ofthe proton beam positioner interconnect 360 can operatively couple theproton beam positioner interconnect 360 to one or more of a powerswitch, a power reset switch, one or more patient proton beampositioning motors, one or more patient proton beam rotational motors,and the like. The proton beam positioner interconnect 360 may includeone or more physical monitoring contacts coupled to, integrated with,detachably attached to, or the like, the patient proton beam of theproton beam delivery system 140 or 142. As one example, the controlcontacts 362 of the proton beam positioner interconnect 360 canoperatively couple the proton beam positioner interconnect 360 to one ormore of a component voltage sensor, a component current sensor, one ormore proton beam position sensors, one or more proton beam anglesensors, and the like. The proton beam positioner interconnect 360 mayinclude one or more logical or electronic devices including but notlimited to jumper contacts, solder contacts, integrated circuits, logicgates, flip flops, gate arrays, programmable gate arrays, and the like.

The proton beam energy interconnect 370 is operable to operativelycouple an electrical, electronic, or like component of at least oneproton beam actuator of the proton beam delivery system 140 or 142respectively to the component interface channel 240 or 242. The protonbeam energy interconnect 370 may include one or more physical controlcontacts 372 coupled to, integrated with, detachably attached to, or thelike, at least one motorized actuator of the proton beam delivery system140 or 142. As one example, the control contacts 372 of the proton beamenergy interconnect 370 can operatively couple the proton beam energyinterconnect 370 to one or more of a power switch, a power reset switch,one or more patient proton beam positioning motors, one or more patientproton beam rotational motors, and the like. The proton beam energyinterconnect 370 may include one or more physical monitoring contactscoupled to, integrated with, detachably attached to, or the like, thepatient proton beam of the proton beam delivery system 140 or 142. Asone example, the control contacts 372 of the proton beam energyinterconnect 370 can operatively couple the proton beam energyinterconnect 370 to one or more of a component voltage sensor, acomponent current sensor, one or more proton beam distribution sensors,one or more proton beam density sensors, and the like. The proton beamenergy interconnect 370 may include one or more logical or electronicdevices including but not limited to jumper contacts, solder contacts,integrated circuits, logic gates, flip flops, gate arrays, programmablegate arrays, and the like.

The patient positioner interconnect 380 is operable to operativelycouple an electrical, electronic, or like component of at least onepatient positioner of the proton beam delivery system 140 or 142respectively to the component interface channel 240 or 242. The patientpositioner interconnect 380 may include one or more physical controlcontacts 382 coupled to, integrated with, detachably attached to, or thelike, at least one motorized actuator of the proton beam delivery system140 or 142. As one example, the control contacts 382 of the patientpositioner interconnect 380 can operatively couple the patientpositioner interconnect 380 to one or more of a power switch, a powerreset switch, one or more patient alignment positioning motors, one ormore patient alignment rotational motors, and the like. The patientpositioner interconnect 380 may include one or more physical monitoringcontacts coupled to, integrated with, detachably attached to, or thelike, the patient alignment of the proton beam delivery system 140 or142. As one example, the control contacts 382 of the patient positionerinterconnect 380 can operatively couple the patient positionerinterconnect 380 to one or more of a component voltage sensor, acomponent current sensor, one or more patient alignment positionsensors, one or more patient alignment angle sensors, and the like. Thepatient positioner interconnect 380 may include a positioner feedbackcomponent operable to modify one or more of position and orientation ofone or more of a table, chair, or gantry with respect to a particularportion of a body of a biological organism, patient, and the like. Thepatient positioner interconnect 380 may include one or more logical orelectronic devices including but not limited to jumper contacts, soldercontacts, integrated circuits, logic gates, flip flops, gate arrays,programmable gate arrays, and the like.

The imager interconnect 390 is operable to operatively couple anelectrical, electronic, or like component of at least one proton beamactuator of the proton beam delivery system 140 or 142 respectively tothe component interface channel 240 or 242. The imager interconnect 390may include one or more physical control contacts 392 coupled to,integrated with, detachably attached to, or the like, at least onemotorized actuator of the proton beam delivery system 140 or 142. As oneexample, the control contacts 392 of the imager interconnect 390 canoperatively couple the imager interconnect 390 to one or more of a powerswitch, a power reset switch, one or more patient proton beampositioning motors, one or more patient proton beam rotational motors,and the like. The imager interconnect 390 may include one or morephysical monitoring contacts coupled to, integrated with, detachablyattached to, or the like, the patient proton beam of the proton beamdelivery system 140 or 142. As one example, the control contacts 392 ofthe imager interconnect 390 can operatively couple the imagerinterconnect 390 to one or more of a component voltage sensor, acomponent current sensor, a brightness sensor, a color sensor, a visualsensor, an infrared sensor, and the like. The imager interconnect 390may include one or more logical or electronic devices including but notlimited to jumper contacts, solder contacts, integrated circuits, logicgates, flip flops, gate arrays, programmable gate arrays, and the like.

FIG. 4 illustrates an example proton beam emitting component interface,further to the example proton beam system gateway of FIG. 2. Asillustrated by way of example in FIG. 4, an example proton beam emittingcomponent interface 400 includes at least one hydrogen supplyinterconnect 410, at least one proton beam power interconnect 420, atleast one proton beam formation interconnect 430, at least one cyclotroninterconnect 440, and at least one proton beam transporter interconnect450.

The hydrogen supply interconnect 410 is operable to operatively couplean electrical, electronic, or like component of at least one hydrogensupply of the proton beam emitting system 130 to the component interfacechannel 250. The hydrogen supply interconnect 410 may include one ormore physical control contacts 412 coupled to, integrated with,detachably attached to, or the like, at least one motorized actuator ofthe proton beam emitting system 130. As one example, the controlcontacts 412 of the hydrogen supply interconnect 410 can operativelycouple the hydrogen supply interconnect 410 to one or more of a powerswitch, a power reset switch, a hydrogen gas flow controller, a liquidhydrogen flow controller, an ionic hydrogen generator, and the like. Thehydrogen supply interconnect 410 may include one or more physicalmonitoring contacts coupled to, integrated with, detachably attached to,or the like, the hydrogen supply of the proton beam emitting system 130.As one example, the control contacts 412 of the hydrogen supplyinterconnect 410 can operatively couple the hydrogen supply interconnect410 to one or more of a component voltage sensor, a component currentsensor, a hydrogen flow rate sensor, a hydrogen charge level sensor, ahydrogen supply temperature sensor, and the like. The hydrogen supplyinterconnect 410 may include one or more logical or electronic devicesincluding but not limited to jumper contacts, solder contacts,integrated circuits, logic gates, flip flops, gate arrays, programmablegate arrays, and the like.

The proton beam power interconnect 420 is operable to operatively couplean electrical, electronic, or like component of at least one proton beamgenerator of the proton beam emitting system 130 to the componentinterface channel 250. The proton beam power interconnect 420 mayinclude one or more physical control contacts 422 coupled to, integratedwith, detachably attached to, or the like, at least one motorizedactuator of the proton beam emitting system 130. As one example, thecontrol contacts 422 of the proton beam power interconnect 420 canoperatively couple the proton beam power interconnect 420 to one or moreof a power switch, a power reset switch, a current source controller, avoltage source controller, and the like. The proton beam powerinterconnect 420 may include one or more physical monitoring contactscoupled to, integrated with, detachably attached to, or the like, theproton beam generator of the proton beam emitting system 130. As oneexample, the control contacts 422 of the proton beam power interconnect420 can operatively couple the proton beam power interconnect 420 to oneor more of a component voltage sensor, a component current sensor, aproton beam output magnitude sensor, a proton beam generator temperaturesensor, and the like. The proton beam power interconnect 420 may includeone or more logical or electronic devices including but not limited tojumper contacts, solder contacts, integrated circuits, logic gates, flipflops, gate arrays, programmable gate arrays, and the like.

The proton beam formation interconnect 430 is operable to operativelycouple an electrical, electronic, or like component of at least oneproton beam generator of the proton beam emitting system 130 to thecomponent interface channel 250. The proton beam formation interconnect430 may include one or more physical control contacts 432 coupled to,integrated with, detachably attached to, or the like, at least onemotorized actuator of the proton beam emitting system 130. As oneexample, the control contacts 432 of the proton beam formationinterconnect 430 can operatively couple the proton beam formationinterconnect 430 to one or more of a power switch, a power reset switch,a current source controller, a voltage source controller, and the like.The proton beam formation interconnect 430 may include one or morephysical monitoring contacts coupled to, integrated with, detachablyattached to, or the like, the proton beam generator of the proton beamemitting system 130. As one example, the control contacts 432 of theproton beam formation interconnect 430 can operatively couple the protonbeam formation interconnect 430 to one or more of a component voltagesensor, a component current sensor, a proton beam output magnitudesensor, a proton beam distribution sensor, and the like. The sensors ofthe proton beam formation interconnect 430 can detect characteristics ofa proton beam at or near the point of generation of the proton beam, asopposed to corresponding proton beam delivery sensors that can detectcharacteristics of the proton beam at or near a point of application.The proton beam formation interconnect 430 may include one or morelogical or electronic devices including but not limited to jumpercontacts, solder contacts, integrated circuits, logic gates, flip flops,gate arrays, programmable gate arrays, and the like.

The cyclotron interconnect 440 is operable to operatively couple anelectrical, electronic, or like component of at least one proton beamgenerator of the proton beam emitting system 130 to the componentinterface channel 250. The cyclotron interconnect 440 may include one ormore physical control contacts 442 coupled to, integrated with,detachably attached to, or the like, at least one motorized actuator ofthe proton beam emitting system 130. As one example, the controlcontacts 442 of the cyclotron interconnect 440 can operatively couplethe cyclotron interconnect 440 to one or more of a power switch, a powerreset switch, a current source controller, a voltage source controller,and the like. The cyclotron interconnect 440 may include one or morephysical monitoring contacts coupled to, integrated with, detachablyattached to, or the like, the proton beam generator of the proton beamemitting system 130. As one example, the control contacts 442 of thecyclotron interconnect 440 can operatively couple the cyclotroninterconnect 440 to one or more of a component voltage sensor, acomponent current sensor, a proton generation rate sensor, a hydrogenintake rate sensor, a particle accelerator energy level sensor, and thelike. The sensors of the cyclotron interconnect 440 can detectcharacteristics of a proton beam at or near the point of generation ofthe proton beam, as opposed to corresponding proton beam deliverysensors that can detect characteristics of the proton beam at or near apoint of application. The cyclotron interconnect 440 may include one ormore logical or electronic devices including but not limited to jumpercontacts, solder contacts, integrated circuits, logic gates, flip flops,gate arrays, programmable gate arrays, and the like.

The proton beam transporter interconnect 450 is operable to operativelycouple an electrical, electronic, or like component of at least oneproton beam generator of the proton beam emitting system 130 to thecomponent interface channel 250. The proton beam transporterinterconnect 450 may include one or more physical control contacts 452coupled to, integrated with, detachably attached to, or the like, atleast one motorized actuator of the proton beam emitting system 130. Asone example, the control contacts 452 of the proton beam transporterinterconnect 450 can operatively couple the proton beam transporterinterconnect 450 to one or more of a power switch, a power reset switch,a current source controller, a voltage source controller, and the like.The proton beam transporter interconnect 450 may include one or morephysical monitoring contacts coupled to, integrated with, detachablyattached to, or the like, the proton beam generator of the proton beamemitting system 130. As one example, the control contacts 452 of theproton beam transporter interconnect 450 can operatively couple theproton beam transporter interconnect 450 to one or more of a proton beamvoltage sensor, a proton beam current sensor, a proton flow rate sensor,a proton beam charge sensor, and the like. The sensors of the protonbeam transporter interconnect 450 can detect characteristics of a protonbeam at or near one or more points of splitting of the proton beam froma proton beam emitting system 130 to one or more proton beam deliverysystems 140 and 142, as opposed to corresponding proton beam deliverysensors that can detect characteristics of the proton beam at or near apoint of application. The proton beam transporter interconnect 450 mayinclude one or more logical or electronic devices including but notlimited to jumper contacts, solder contacts, integrated circuits, logicgates, flip flops, gate arrays, programmable gate arrays, and the like.

FIG. 5 illustrates an example system memory, further to the exampleproton beam system gateway of FIG. 2. As illustrated by way of examplein FIG. 5, an example system memory 500 includes an operating system510, a component state engine 520, a component topology engine 530, acontrol authorization engine 540, a network interface engine 550, and adevice command processor 560.

The operating system 510 includes hardware control instructions andprogram execution instructions. The operating system 510 may be a highlevel operating system, a server operating system, an embedded operatingsystem, or a boot loader. The operating system 510 may include one ormore instructions operable specifically with or only with the systemprocessor 210. The operating system 510 may be operable to controlexecution of one or more of the component state engine 520, thecomponent topology engine 530, the control authorization engine 540, thenetwork interface engine 550, and the device command processor 560.

The component state engine 520 is operable to identify one or moreoperating states associated with one or more components of one or moreof the proton beam emitting system 130 and the first and second protonbeam delivery systems 140 and 142. As one example, operating states caninclude an operational state and a fault state. An example operationalstate can indicate that a component is operating normally, is not inneed of servicing, or the like. An example fault state can indicate thata component is not operating normally, is in need of servicing, or thelike. The component state engine 520 can identify operating states basedon input received from one or more of the interconnects of the protonbeam delivery component interfaces 300 and 302 and the proton beamemitting component interface 400. The component state engine 520 mayinclude at least one of a component state processor 522 and a componentinterlock processor 524.

The component state processor 522 is operable to determine at least oneoperating state of at least one corresponding component based on inputfrom one or more of the interconnects of the proton beam deliverycomponent interfaces 300 and 302 and the proton beam emitting componentinterface 400. In some implementations, the component state processor522 includes an operating state translation portion operable to convertan operating state input into an operating state. As one example, thecomponent state processor 522 can associate an operating state inputsatisfying an operating state threshold with an operational state, andcan associate an operating state input not satisfying an operating statethreshold with a fault state. As another example, an operating statethreshold can be a particular voltage level, current level, hydrogenflow rate, flow rate, charge level, or the like. The component stateprocessor 522 may be operable to obtain one or more operating statethresholds from at least one interlock template associated with acorresponding component. The interlock template can include a structureddata file. As one example, the interlock template can be an XML, file orthe like. The interlock template may correspond to a particularconfiguration of the proton beam emitting system 130 and the first andsecond proton beam delivery systems 140 and 142. The interlock templatemay correspond to a particular configuration associated with aparticular model or type of beam emitting system or beam delivery systemcorresponding respectively to the proton beam emitting system 130 andthe first and second proton beam delivery systems 140 and 142.

The component interlock processor 524 is operable to determine at leastone operating state of at least one corresponding device including atleast one component based on input from one or more of the interconnectsof the proton beam delivery component interfaces 300 and 302 and theproton beam emitting component interface 400. The component interlockprocessor 524 may be operable to obtain one or more device interlockrelationships with respect to one or more components from the interlocktemplate associated with the corresponding component and device. Theinterlock template may include a dependency relationship between one ormore components and one or more devices including the components. As oneexample, the interlock template can define an interlock sensor deviceincluding multiple sensor components, each configured to detect adifferent characteristic. As another example, an interlock cancorrespond to a collection of components, and can correspond to a deviceincluding those components. Thus, an interlock can be interchangeablewith a device with respect to a control and monitoring context.

The component topology engine 530 is operable to generate arepresentation of at least a portion of the proton beam emitting system130 and the first and second proton beam delivery systems 140 and 142 inaccordance with multiple representation structures. The componenttopology engine 530 may obtain a representation structure based on inputreceived from an interlock template associated with the proton beamemitting system 130 and the first and second proton beam deliverysystems 140 and 142. As one example, the component topology engine 530can generate a hierarchical topology corresponding to an interlockincluding components, a greater interlock including an interlock, agreater interlock including an interlock and a component, anycombination thereof, or the like. As another example, the componenttopology engine 530 can generate a schematic topology corresponding toone or more operatively coupling between components, interlock, or anycombination thereof, within at least a portion of at least one of theproton beam emitting system 130 and the first and second proton beamdelivery systems 140 and 142. The component topology engine 530 mayinclude at least one of a hierarchy processing engine 532 and aschematic processing engine 534.

The hierarchy processing engine 532 is operable to generate arepresentation of at least a portion of the proton beam emitting system130 and the first and second proton beam delivery systems 140 and 142 inaccordance with a hierarchical representation structure. As one example,a hierarchical presentation structure can include a nested list ofcomponents and interlocks. As another example, a hierarchical structurecan include one or more components nested under respective interlocks,and can further include interlocks further nested under additionalinterlocks in a multilevel hierarchical structure. A hierarchicalstructure can include a portion of a hierarchy corresponding to at leastone of the proton beam emitting system 130 and the first and secondproton beam delivery systems 140 and 142. As one example, a portion of ahierarchy can include a subset of interlocks and the components orinterlocks contained thereby. Thus, hierarchy processing engine 532 maygenerate a portion of a hierarchical structure corresponding to acollection of at least one interlock or component associated with acontaining or like relationship therebetween. As one example, acontaining relationship can be a relationship where a component isintegrated into an interlock or device corresponding to an interlock.

The schematic processing engine 534 is operable to generate arepresentation of at least a portion of the proton beam emitting system130 and the first and second proton beam delivery systems 140 and 142 inaccordance with a schematic representation structure. As one example, aschematic presentation structure can include a blueprint structure, anengineering structure, an electrical structure, a block structure, orthe like including one or more components and interlocks. As anotherexample, a schematic structure can include one or more components andinterlocks operatively coupled in an arrangement corresponding to aphysical structure of the components and interlocks. A schematicstructure can include a portion of a schematic corresponding to at leastone of the proton beam emitting system 130 and the first and secondproton beam delivery systems 140 and 142. As one example, a portion of aschematic can include a subset of interlocks and the components orinterlocks connected thereto, directly or indirectly. Thus, schematicprocessing engine 534 may generate a portion of a schematic structurecorresponding to a collection of at least one interlock or componentassociated with a coupling, connecting, or like relationshiptherebetween. As one example, a connecting relationship can be arelationship where a component is electrically connected or physicallyattached to an interlock or device corresponding to an interlock.

The control authorization engine 540 is operable to authorize executionof one or more control instructions to modify one or more operatingstates of one or more components of one or more of the proton beamemitting system 130 and the first and second proton beam deliverysystems 140 and 142. The control authorization engine 540 may beoperable to accept one or more control authorization indications duringa predetermined control authorization instruction acceptance period. Theacceptance period may correspond to a period in seconds, minutes duringwhich a control authorization instruction may be validly received. Whena control authorization instruction is validly received, the controlauthorization engine 540 can allow execution of control instructions. Asone example, the control authorization engine 540 can allow execution ofcontrol instructions by allowing transmission of a control instructionfrom the device command processor 564 to the network interface engine550. When a control authorization instruction is not validly received,the control authorization engine 540 can block execution of controlinstructions. As one example, the control authorization engine 540 canblock execution of control instructions by blocking transmission of acontrol instruction from the device command processor 564 to the networkinterface engine 550. The control authorization engine 540 may includean authorization input engine 542.

The authorization input engine 542 is operable to receive input from thecontrol authorization toggle switch 150 and to receive, generate,obtain, or the like, a control authorization instruction in response tothe input from the control authorization toggle switch 150. Theauthorization input engine 542 may receive one or more of an analogsignal, a digital signal, a binary signal, or any combination thereof,from the control authorization toggle switch 150.

The network interface engine 550 is operable to communicate one or morecontrol instructions, operating states, control information, monitoringinformation, any combination thereof, or the like, to any of thecomponent interfaces 300, 302 and 400, and communication interfaces 220and 230. The network interface engine 550 may include at least one of aninterconnect interface controller 552, a control interface controller554, and a monitor interface controller 556.

The interconnect interface controller 552 is operable to communicate oneor more control instructions, operating states, control information,monitoring information, any combination thereof, or the like, to any ofthe component interfaces 300, 302 and 400. The interconnect interfacecontroller 552 may be operable to transmit analog signals, digitalsignals, any combination thereof, or the like, to any interconnectoperatively coupled to any of the component interfaces 300, 302 and 400.The interconnect interface controller 552 can transmit instructions inaccordance and compatible with any analog or digital channel, wire,trace, or the like operatively coupled to any of the componentinterfaces 300, 302 and 400.

The control interface controller 554 is operable to communicate one ormore control instructions, control information, any combination thereof,or the like, by the system control communication interface 220. Thecontrol interface controller 554 may be operable to transmit and receivea secure, dedicated, tunneled, packetized, encrypted, tokenized, or likecommunication by the system control communication interface 220. Thecontrol interface controller 554 can transmit instructions in accordanceand compatible with any network channel, wireless channel,telecommunication channel, or the like operatively coupled to the systemcontrol communication interface 220.

The monitor interface controller 556 is operable to communicate one ormore monitoring instructions, operating states, monitoring information,any combination thereof, or the like, by the system monitorcommunication interface 230. The monitor interface controller 556 may beoperable to transmit and receive a secure, dedicated, tunneled,packetized, encrypted, tokenized, or like communication by the systemmonitor communication interface 230. The monitor interface controller556 can transmit instructions in accordance and compatible with anynetwork channel, wireless channel, telecommunication channel, or thelike operatively coupled to system control communication interface 220.The control interface controller 554 and the monitor interfacecontroller 556 can advantageously be decoupled, isolated, or the like,from each other to ensure independent and secure communication for bothsecure control of proton beam hardware and reliable monitoring of protonbeam hardware.

The device command processor 560 is operable to generate a devicecommand executable by or at any of the interconnects 310, 320, 330, 340,350, 360, 370, 380, 390, 410, 420, 430, 440 and 450. The device commandprocessor 560 may include an interconnect command translator 562. Theinterconnect command translator 562 is operable to generate at least onedevice command compatible with at least one of the interconnects 310,320, 330, 340, 350, 360, 370, 380, 390, 410, 420, 430, 440 and 450 tomodify an operating state of at least one component coupled thereto.

FIG. 6 illustrates an example diagnostic system, further to the examplesystem of FIG. 1. As illustrated by way of example in FIG. 6, an examplediagnostic system 600 includes a system processor 610, a system memory700, a diagnostic control communication interface 620, a diagnosticmonitor communication interface 630, one or more input devices 640, anda display 650.

The system processor 610 is operable to execute one or more instructionsassociated with input from the diagnostic control communicationinterface 620, the diagnostic monitor communication interface 630, theinput devices 640, and the display 650. The system processor 610 cancorrespond in one or more of structure and operation to the systemprocessor 210. The system memory 700 is operable to store dataassociated with the diagnostic system 600. The system memory 700 cancorrespond in one or more of structure and operation to the systemmemory 500.

The diagnostic control communication interface 620 is operable toreceive and transmit one or more instructions by the service controlchannel 102 to the proton beam system gateway 200. The diagnosticcontrol communication interface 620 may include a command translationunit operable to convert one or more instructions between a processorformat compatible with the system processor 610 and a communicationformat compatible with one or more of the service control channel 102and the proton beam system gateway 200. The diagnostic controlcommunication interface 620 may include one or more logical orelectronic devices including but not limited to integrated circuits,logic gates, flip flops, gate arrays, programmable gate arrays, and thelike. Any electrical, electronic, or like devices, or componentsassociated with the diagnostic control communication interface 620 canalso be associated with, integrated with, integrable with, replaced by,supplemented by, complemented by, or the like, the system processor 610or any component thereof.

The diagnostic monitor communication interface 630 is operable toreceive and transmit one or more instructions by the service monitorchannel 104 to the proton beam system gateway 200. The diagnosticmonitor communication interface 630 may include a command translationunit operable to convert one or more instructions between a processorformat compatible with the system processor 610 and a communicationformat compatible with one or more of the service monitor channel 104and the proton beam system gateway 200. The diagnostic monitorcommunication interface 630 may include one or more logical orelectronic devices including but not limited to integrated circuits,logic gates, flip flops, gate arrays, programmable gate arrays, and thelike. Any electrical, electronic, or like devices, or componentsassociated with the diagnostic monitor communication interface 630 canalso be associated with, integrated with, integrable with, replaced by,supplemented by, complemented by, or the like, the system processor 610or any component thereof.

The input devices 640 are operable to receive control instructions andmonitoring instructions. The input devices may receive instructions froma user by one or more human-computer interface devices. As one example,human-computer interface devices can include one or more notebookcomputers, desktop computers, tablets, smartphones, printers, scanners,telephony endpoints, videoconferencing endpoints, keyboards, mice,trackpads, gaming peripherals, monitors, televisions, and the like. Thedisplay 650 is operable to display one or more graphical user interfacesfor remote control and remote monitoring. In some implementations, thedisplay 650 includes an electronic display. The electronic display mayinclude a liquid crystal display (LCD), a light-emitting diode (LED)display, an organic light-emitting diode (OLED) display, or the like.

FIG. 7 illustrates an example system memory further to the examplediagnostic system of FIG. 6. As illustrated by way of example in FIG. 7,an example system memory 700 includes an operating system 710, aninterface input engine 720, a network interface engine 730, and apresentation engine 740.

The operating system 710 includes hardware control instructions andprogram execution instructions. The operating system 710 may be a highlevel operating system, a server operating system, a desktop operatingsystem, an embedded operating system, or a boot loader The operatingsystem 710 may include one or more instructions operable specificallywith or only with the system processor 610. The operating system 710 maybe operable to control execution of one or more of the interface inputengine 720, the network interface engine 730, and the presentationengine 740. The interface input engine 720 is operable to obtain one ormore inputs from one or more of the input devices 640. As one example,the interface input engine 720 includes one or more instructions forobtaining, parsing, combining, translating, or any combination thereof,or the like, input from at least one of the input devices 640.

The network interface engine 730 is operable to communicate one or morecontrol instructions, operating states, control information, monitoringinformation, any combination thereof, or the like, to any of thecommunication interfaces 620 and 630. The network interface engine 730may include a control interface controller 732 and a monitor interfacecontroller 734. The control interface controller 732 is operable tocommunicate one or more control instructions, control information, anycombination thereof, or the like, by the diagnostic controlcommunication interface 620. The control interface controller 732 may beoperable to transmit and receive a secure, dedicated, tunneled,packetized, encrypted, tokenized, or like communication by thediagnostic control communication interface 620. The control interfacecontroller 732 can transmit instructions in accordance and compatiblewith any network channel, wireless channel, telecommunication channel,or the like operatively coupled to the diagnostic control communicationinterface 620.

The monitor interface controller 734 is operable to communicate one ormore monitoring instructions, operating states, monitoring information,any combination thereof, or the like, by the diagnostic monitorcommunication interface 630. The monitor interface controller 734 may beoperable to transmit and receive a secure, dedicated, tunneled,packetized, encrypted, tokenized, or like communication by thediagnostic monitor communication interface 630. The monitor interfacecontroller 734 can transmit instructions in accordance and compatiblewith any network channel, wireless channel, telecommunication channel,or the like operatively coupled to diagnostic monitor communicationinterface 630. The control interface controller 732 and the monitorinterface controller 734 can advantageously be decoupled, isolated, orthe like, from each other to ensure independent and secure communicationfor both secure control of proton beam hardware and reliable monitoringof proton beam hardware.

The presentation engine 740 is operable to generate one or moregraphical user interfaces, presentations, control affordances, operatingstate indications, hierarchies, schematics, and the like associated withone or more of the proton beam emitting system 130, the proton beamdelivery systems 140 and 142, the proton beam system gateway 200, thecontrol authorization toggle switch 160, and the diagnostic system 600.The presentation engine 740 may be operable to modify any presentationin response to any user input, control instruction, monitoringinstruction, or the like, received thereby. The presentation engine 740may include at least one of a hierarchy presentation engine 742, aschematic presentation engine 744, an interlock presentation engine 746,and a user presentation controller 748.

The hierarchy presentation engine 742 is operable to generate at leastone hierarchical presentation having a hierarchical structurecorresponding to at least a portion of one or more of the proton beamemitting system 130, the proton beam delivery systems 140 and 142, theproton beam system gateway 200, and the control authorization toggleswitch 160. The hierarchy presentation engine 742 may be operable togenerate a hierarchical presentation based on a hierarchy generated byor at the component topology engine 530 or the hierarchy processingengine 532. The hierarchy presentation engine 742 may be operable totraverse at least a portion of a hierarchy generated by or at thecomponent topology engine 530 or the hierarchy processing engine 532, togenerate the hierarchical presentation. As one example, the hierarchypresentation engine 742 can generate a hierarchy having a nested liststructure, including an operating state indicator associated with one ormore items in the nested list. As another example, the operating stateindicator can include an icon, glyph, coloration, image, character, orany combination thereof, or the like.

The schematic presentation engine 744 is operable to generate at leastone schematic presentation having a schematic structure corresponding toat least a portion of one or more of the proton beam emitting system130, the proton beam delivery systems 140 and 142, the proton beamsystem gateway 200, and the control authorization toggle switch 160. Theschematic presentation engine 744 may be operable to generate aschematic presentation based on a schematic generated by or at thecomponent topology engine 530 or the schematic processing engine 534.The schematic presentation engine 744 may be operable to traverse atleast a portion of a schematic generated by or at the component topologyengine 530 or the schematic processing engine 534, to generate theschematic presentation. As one example, the schematic presentationengine 744 can generate a schematic having a blueprint structure,including an operating state indicator associated with one or more itemsin the blueprint. As another example, the operating state indicator caninclude an icon, glyph, coloration, image, character, or any combinationthereof, or the like.

The interlock presentation engine 746 is operable to generate one ormore operating indicator presentations in accordance with one or moreinterlock dependency conditions. An interlock dependency condition maycorrespond to an absolute component dependency, where an interlock isassociated with a fault state if a particular component thereof isassociated with the fault state. An interlock dependency condition maycorrespond to an independent component dependency, where an interlock isnot associated with a fault state even if a particular component thereofis associated with the fault state. The interlock presentation engine746 may generate the operating indicator presentations in accordancewith at least one of the component state engine 520 and the componentinterlock processor 524.

The user presentation controller 748 is operable to generate one or moreuser interfaces based on a user type associated with the user interface.As one example, the user presentation controller 748 can generate a userinterface with a clinician view if a user type linked to the userpresentation controller 748 corresponds to a clinician. The clinicianview may include a simplified user interface associated with one or moreof the hierarchical presentation and the schematic presentation, inwhich component-level presentation are omitted. As another example, theuser presentation controller 748 can generate a user interface with atechnician view if a user type linked to the user presentationcontroller 748 corresponds to a technician. The technician view mayinclude a detailed user interface associated with one or more of thehierarchical presentation and the schematic presentation, in whichcomponent-level presentation are included. The clinician view may beincluded within the technician view as a portion thereof.

FIG. 8 illustrates a first example graphical user interface for remotemonitoring of a proton beam emitting and delivery system, in accordancewith present implementations. As illustrated by way of example in FIG.8, an example graphical user interface 800 includes a delivery systemreport interface 810, a system overview report interface 820, an imagerreport interface 830, a scanning or eye nozzle report interface 840, agantry actuator report interface 850, and a table or chair actuatorreport interface 860.

The delivery system report interface 810 includes a portion of thegraphical user interface 800 presenting one or more characteristics of aproton beam delivery system among the first and second proton beamdelivery systems 140 and 142. As one example, the delivery system reportinterface 810 can present one or more of a software version number,identifier, or the like executing at the proton beam delivery system 140or 142, a delivery facility state indicating whether the proton beamdelivery systems 140 or 142 is operational, a robot state indicatingwhether a robotic system associated with the proton beam delivery system140 or 142 is operational, and a system temperature associated with theproton beam delivery systems 140 or 142. A robot state can includeindividually or collectively one or more actuators, motors, positions,and the like associated with the proton beam delivery system 140 or 142.The delivery system report interface 810 can advantageously present anintuitive and near-real-time system-level presentation directly obtainedfrom interconnects for one or more interconnects to the proton beamdelivery system 140 or 142.

The system overview report interface 820 includes a portion of thegraphical user interface 800 presenting one or more interlock statesassociated with the proton beam delivery system 140 or 142. The systemoverview report interface 820 may present a flat or non-hierarchicallist view of one or more interlocks associated with the proton beamdelivery system 104 or 142. The system overview report interface 820 canalso include one or more operating state indicators corresponding to oneor more of the interlocks presented at the system overview reportinterface 820. The system overview report interface 820 canadvantageously present an intuitive and near-real-time interlock-levelpresentation directly obtained from interconnects for one or moreinterconnects to the proton beam delivery system 140 or 142.

The imager report interface 830 includes a portion of the graphical userinterface 800 presenting one or more characteristics of a proton beamdelivery imager device among the first and second proton beam deliverysystems 140 and 142. As one example, the imager report interface 830 canpresent one or more of an orientation state of a proton beam deliveryimager device and one or more interlocks and their correspondingoperating state indicators. As one example, an orientation state of theproton beam delivery imager device can include a first positionconfiguration state indicating one or more lateral or angular positionscorresponding to the first position configuration state, and a secondposition configuration state indicating one or more lateral or angularpositions corresponding to the second position configuration state. Theimager report interface 830 can advantageously present an intuitive andnear-real-time interlock-level presentation directly obtained frominterconnects for one or more interconnects to the proton beam deliverysystem 140 or 142.

The scanning or eye nozzle report interface 840 includes a portion ofthe graphical user interface 800 presenting one or more characteristicsof a proton beam scanning nozzle device or a proton beam eye nozzledevice among the first and second proton beam delivery systems 140 and142. As one example, the scanning or eye nozzle report interface 840 canpresent one or more of an orientation state of a proton beam scanningnozzle device or a proton beam eye nozzle device and one or moreinterlocks and their corresponding operating state indicators. As oneexample, an orientation state of the proton beam scanning nozzle deviceor the proton beam eye nozzle device can include one or more lateral orangular positions corresponding thereto. The scanning or eye nozzlereport interface 840 can advantageously present an intuitive andnear-real-time interlock-level presentation directly obtained frominterconnects for one or more interconnects to the proton beam deliverysystem 140 or 142. The scanning or eye nozzle report interface 840 mayinclude a scanning or eye nozzle aperture interface 842.

The scanning or eye nozzle aperture interface 842 may include a portionof the graphical user interface 800 presenting one or more proton beamdistribution indications, calibration indications, or the like of aproton beam scanning nozzle device or a proton beam eye nozzle deviceamong the first and second proton beam delivery systems 140 and 142. Asone example, the scanning or eye nozzle report interface 840 can presentone or more distribution indications located at actual locations ofdistribution of proton beam energy as operating state indicators withrespect to a frame. As another example, the scanning or eye nozzlereport interface 840 can present one or more calibration indicationslocated at theoretical or ideal locations of distribution of proton beamenergy as operating state indicators with respect to a frame. The framemay correspond to a cross-section of a proton beam at a point of receiptat the first or second proton beam delivery system 140 or 142, or pointof application corresponding to a patient or the like. As one example,an orientation state of the proton beam scanning nozzle device or theproton beam eye nozzle device can include one or more lateral or angularpositions corresponding thereto.

The gantry actuator report interface 850 includes a portion of thegraphical user interface 800 presenting one or more characteristics ofone or more gantry motors and sensors among the first and second protonbeam delivery systems 140 and 142. As one example, the gantry actuatorreport interface 850 can present one or more of an orientation state ofa gantry and one or more interlocks and their corresponding operatingstate indicators. The table or chair actuator report interface 860includes a portion of the graphical user interface 800 presenting one ormore characteristics of one or more table or chair motors and sensorsamong the first and second proton beam delivery systems 140 and 142. Asone example, the table or chair actuator report interface 860 canpresent one or more of an orientation state of a table or chair and oneor more interlocks and their corresponding operating state indicators.The gantry actuator report interface 850 and the table or chair actuatorreport interface 860 can advantageously present an intuitive andnear-real-time interlock-level presentation directly obtained frominterconnects for one or more interconnects to the proton beam deliverysystem 140 or 142.

FIG. 9 illustrates a second example graphical user interface for remotemonitoring of a proton beam emitting and delivery system including ahierarchical presentation, in accordance with present implementations.As illustrated by way of example in FIG. 9, an example graphical userinterface 900 includes a delivery system clinical report interface 910,a hierarchy presentation interface 920, a beam delivery queue interface930, and a clinical operating interface 940.

The delivery system clinical report interface 910 includes a portion ofthe graphical user interface 900 presenting one or more orientations ofone or more motors and sensors among the first and second proton beamdelivery systems 140 and 142. The delivery system clinical reportinterface 910 can advantageously present clinician-centric operatingstates associated with the first or second proton beam delivery systems140 or 142 to improve ability to remotely monitor and remotely controlthe first or second proton beam delivery system 140 or 142 by thediagnostic system 600. The delivery system clinical report interface 910may include at least one of a positioner state interface 912 and apositioner state queue interface 914. The positioner state interface 912may present a current state of one or more of a scanning nozzle, eyenozzle, gantry, table, and chair in connection with a clinicaloperation, treatment, or the like. The positioner state queue interface914 may present at least one past or future state of one or more of ascanning nozzle, eye nozzle, gantry, table, and chair in connection witha clinical operation, treatment, or the like. As one example, thepositioner state queue interface 914 can present at least one past orfuture state as a list, queue, or the like ordered by time with respectto a relative current time or an absolute start or end time of aclinical operation, treatment, or the like.

The hierarchy presentation interface 920 includes a portion of thegraphical user interface 900 presenting one or more interlocks and theircorresponding included components for at least a portion of the first orsecond proton beam delivery systems 140 or 142. The hierarchypresentation interface 920 can advantageously present an intuitive andnear-real-time interface including operating states and cascadingfailure information associated with the first or second proton beamdelivery systems 140 or 142 to improve ability to remotely monitor andremotely control the first or second proton beam delivery systems 140 or142 by the diagnostic system 600. In some implementations, the hierarchypresentation interface 920 includes at least one of first, second, andthird interlock hierarchy presentations 922, 924 and 926. The firstinterlock hierarchy presentation 922 includes a first examplehierarchical presentation free of any fault states. In the first examplehierarchical presentation, operating states of all components and aninterlock including the components are in an operational state.

The second interlock hierarchy presentation 924 includes a secondexample hierarchical presentation including a component fault stateindependent of a fault state of an interlock including the fault statecomponent. In the second example hierarchical presentation, an operatingstate of one component is in a fault state, and an operating state of aninterlock including the component is in an operational state. Thus, inthis example, failure of a component does not cascade to failure of theinterlock. A non-cascading fault state can intuitively indicate a faultstate that needs remote control or monitoring at a lower level ofurgency.

The third interlock hierarchy presentation 926 includes a third examplehierarchical presentation including a component fault state dependent ona fault state of an interlock including the fault state component. Inthe third example hierarchical presentation, an operating state of onecomponent is in a fault state, and an operating state of an interlockincluding the component is in a corresponding fault state in response tothe fault state of the fault state component. Thus, in this example,failure of a component does cascade to failure of the interlock. Acascading fault state can intuitively indicate a fault state that needsremote control or monitoring at a higher level of urgency.

The beam delivery queue interface 930 includes a portion of thegraphical user interface 900 presenting an order of activation of thefirst and second proton beam delivery systems 140 and 142. The beamdelivery queue interface 930 can advantageously present aclinician-centric view of real-time activity of the first or secondproton beam delivery system 140 or 142 to improve ability to remotelymonitor and remotely control the first or second proton beam deliverysystem 140 or 142 by the diagnostic system 600. The beam delivery queueinterface 930 may include a beam delivery queue stack 932. The beamdelivery queue stack 932 includes a portion of the graphical userinterface 900 presenting an order of activation of the first and secondproton beam delivery systems 140 and 142. The beam delivery queue stack932 can include more or fewer stacked elements based on the number ofproton beam delivery systems operatively coupled to the graphical userinterface 900.

The clinical operating interface 940 includes a portion of the graphicaluser interface 900 presenting one or more orientations of one or moreproton beam therapy devices among the first and second proton beamdelivery systems 140 and 142. The beam delivery queue interface 930 canadvantageously present a clinician-centric view of real-time activity ofthe first or second proton beam delivery system 140 or 142 to improveability to remotely monitor and remotely control the first or secondproton beam delivery system 140 or 142 by the diagnostic system 600. Theclinical operating interface 940 may include a proton beam deliverysystem state presentation 942. The proton beam delivery system statepresentation 942 includes a portion of the graphical user interface 900presenting a visual representation of at least one of the first andsecond proton beam delivery systems 140 and 142.

FIG. 10 illustrates a third example graphical user interface for remotecontrol and remote monitoring of a proton beam emitting and deliverysystem including an interlock schematic presentation, in accordance withpresent implementations. As illustrated by way of example in FIG. 10, anexample graphical user interface 1000 includes a proton beam centeringmonitoring interface 1010, an interlock-level schematic viewpresentation 1020, and a component control interface 1030.

The proton beam centering monitoring interface 1010 includes a portionof the graphical user interface 1000 presenting one or morecharacteristics of a proton beam scanning nozzle device or a proton beameye nozzle device among the first and second proton beam deliverysystems 140 and 142. As one example, the scanning or eye nozzle reportinterface 840 can present one or more physical positions with respect toa beam application target area of a proton beam scanning nozzle deviceor a proton beam eye nozzle device and one or more interlocks and theircorresponding operating state indicators, and one or more electricalcharacteristics of a proton beam with respect to portions of the beamapplication target area. As one example, the proton beam centeringmonitoring interface 1010 can present a bell curve or the likeindicating a position of highest beam application energy with respect toa center line or the like of the beam application target area. Theproton beam centering monitoring interface 1010 can advantageouslypresent an intuitive and near-real-time beam shape presentation directlyobtained from interconnects for one or more interconnects to the protonbeam delivery system 140 or 142. The proton beam centering monitoringinterface 1010 may include at least one of first and second beam outputpresentations 1012 and 1014. The first and second beam outputpresentations 1012 and 1014 can correspond to outputs associatedrespectively with the beam delivery schematic interlocks 1040 and 1042respectively of the proton beam delivery component interfaces 300 and302.

The interlock-level schematic view presentation 1020 includes a portionof the graphical user interface 1000 presenting a schematic structure ofone or more of the proton beam emitting system 130. The interlock-levelschematic view presentation 1020 can include an arbitrary number of beamdelivery schematic interlocks 1040 corresponding to the number of protonbeam delivery systems operatively coupled to the graphical userinterface 1000. The interlock-level schematic view presentation 1020 mayinclude at least one of a cyclotron schematic interlock 1022, at leastone schematic proton beam path 1024, one or more beam transportschematic interlocks 1026, and one or more beam delivery schematicinterlocks 1040 and 1042.

The cyclotron schematic interlock 1022 includes a portion of thegraphical user interface 1000 presenting a schematic structure of theproton beam emitting system 130. The interlock-level schematic viewpresentation 1020 may present the cyclotron schematic interlock 1022 inrelation to the schematic proton beam path 1024 as it travels from itspoint of generation at the cyclotron of the proton beam emitting system130 through the beam transport system to one or more of the proton beamdelivery systems 140 and 142. The schematic proton beam path 1024includes a portion of the graphical user interface 1000 presenting aschematic structure of the proton beam throughout the clinical site. Theproton beam presented as the schematic proton beam path 1024 may travelby a beam transport path distinct from the channels 150 and 152. Thebeam transport schematic interlocks 1026 include a portion of thegraphical user interface 1000 presenting a schematic structure of one ormore devices of a beam transport system for transmitting a proton beamgenerated at a proton beam emitting system 130 to one or more of theproton beam delivery systems 140 and 142. The beam delivery schematicinterlocks 1040 and 1042 include a portion of the graphical userinterface 1000 presenting a schematic structure of the proton beamdelivery systems 140 and 142. The beam delivery schematic interlocks1040 and 1042 can correspond to the proton beam delivery systems 140 and142. The beam delivery schematic interlocks 1040 and 1042 canadvantageously indicate proton beam presence and characteristics at thecomponent and interlock levels.

The component control interface 1030 includes a portion of the graphicaluser interface 1000 presenting one or more control affordances formodifying operating states of one or systems, interlocks, or componentsof one or more of the proton beam emitting system 130, the first protonbeam delivery system 140, and the second proton beam delivery system142. The component control interface 1030 may include at least one of afacility control interface 1032, an actuator control interface 1034, abeam control interface 1036, and a beam current interface 1038.

The facility control interface 1032 includes a portion of the graphicaluser interface 1000 presenting one or more control affordances formodifying operating states of the proton beam emitting system 130, thefirst proton beam delivery system 140, and the second proton beamdelivery system 142. The facility control interface 1032 can provide acontrol authorization instruction to the diagnostic system 600, bypass acontrol authorization instruction from the control authorization toggleswitch 150 in response to an activation of the setup control affordance,or can require a control authorization instruction from the controlauthorization toggle switch 150 in response to an activation of thesetup control affordance.

The actuator control interface 1034 includes a portion of the graphicaluser interface 1000 presenting one or more control affordances formodifying operating states of one or more of a gantry, chair, table,scanning nozzle, or eye nozzle of one or more of the proton beamdelivery systems 140 and 142. The beam control interface 1036 includes aportion of the graphical user interface 1000 presenting one or morecontrol affordances for modifying operating states of one or more protonbeams generated by the proton beam emitting system 130. As one example,the beam control interface 1036 can effect one or more of an extractoperation, an insert operation an on operation, an off operation, and abeam current magnitude set operation.

FIG. 11 illustrates a fourth example graphical user interface for remotecontrol and remote monitoring of a proton beam emitting and deliverysystem including an interlock schematic presentation and a componentschematic presentation, in accordance with present implementations. Asillustrated by way of example in FIG. 11, an example graphical userinterface includes the interlock-level schematic view presentation 1020,a component-level schematic view presentation 1110, a component controlinterface 1120, and a component status presentation 1130.

The component-level schematic view presentation 1110 includes a portionof the graphical user interface 1000 presenting a schematic structureincluding one or more components of one or more of the proton beamemitting system 130, the first proton beam delivery system 140, and thesecond proton beam delivery system 142. As one example, thecomponent-level schematic view presentation 1110 can present at leastone interlock, and its included components, for the beam deliveryschematic interlock 1040. The component-level schematic viewpresentation 1110 can present any schematic structure corresponding toany portion or entirety of any collection of interlocks or componentsassociated with one or more of the proton beam emitting system 130, theproton beam delivery system 140, and the proton beam delivery system142. The component-level schematic view presentation 1110 may include atleast one operational state component presentation 1112 and at least onefault state component presentation 1114.

The operational state component presentation 1112 includes a portion ofthe graphical user interface 1000 presenting a schematic structurecorresponding to one or more components of one or more of the protonbeam emitting system 130, the first proton beam delivery system 140, andthe second proton beam delivery system 142. The operational statecomponent presentation 1112 can correspond to any component of anyinterlock of any of the proton beam emitting system 130, the firstproton beam delivery system 140, and the second proton beam deliverysystem 142. The operational state component presentation 1112 canadvantageously present a state of a component in real-time to a remotediagnostic system 600. As one example, the operational state componentpresentation 1112 can be a block, glyph, image, object, or the likecorresponding to a generic or particular component.

The fault state component presentation 1114 includes a portion of thegraphical user interface 1000 presenting a schematic structurecorresponding to one or more components of one or more of the protonbeam emitting system 130, the first proton beam delivery system 140, andthe second proton beam delivery system 142, in a fault state. The faultstate component presentation 1114 can correspond to any component of anyinterlock of any of the proton beam emitting system 130, the firstproton beam delivery system 140, and the second proton beam deliverysystem 142. The fault state component presentation 1114 canadvantageously present a fault state of a component in real-time to aremote diagnostic system 600 to further improve remote control andremote monitoring of the component directly. As one example, the faultstate component presentation 1114 can be a block, glyph, image, object,coloration, or the like corresponding to a particular component andincluding a particular fault state block, glyph, image, object,coloration, or the like.

The component control interface 1120 includes a portion of the graphicaluser interface 1100 presenting one or more control affordances formodifying operating states of one or interlocks or components of one ormore of the proton beam emitting system 130, the first proton beamdelivery system 140, and the second proton beam delivery system 142. Thecomponent control interface 1120 may include at least one of aninterlock control power interface 1122, an interlock control latchinterface 1124, and a component control power interface 1126.

The interlock control power interface 1122 includes at least one controlaffordance for modifying an operating state of at least one componentassociated therewith. As one example, the interlock control powerinterface 1122 can send a power on or power off instruction to allcomponents included in the interlock. The interlock control latchinterface 1124 includes at least one control affordance for modifying atleast one latch state of at least one component associated therewith. Alatch state may indicate that an interlock is in one or more of a faultstate and is not authorized for use in a clinical treatment, procedure,operation, or the like. As one example, the interlock control latchinterface 1124 can send an unlatch instruction to a particular componentincluded in the interlock, subsequent to a selection of the interlock atthe component-level schematic view presentation 1110 or the like. Asanother example, the interlock control latch interface 1124 can send anunlatch instruction to every component included in the interlock,subsequent to a selection of the interlock at the component-levelschematic view presentation 1110 or the like. The component controlpower interface 1126 includes at least one control affordance formodifying an operating state of at least one component associatedtherewith. As one example, the component control power interface 1126can send a power on or power off instruction to a particular componentincluded in the interlock, subsequent to a selection of the interlock atthe component-level schematic view presentation 1110 or the like.

The component status presentation 1130 includes a portion of thegraphical user interface 1100 presenting one or more component statesassociated with at least one of the proton beam emitting system 130, thefirst proton beam delivery system 140, and the second proton beamdelivery system 142. The component status presentation 1130 may presenta flat or non-hierarchical list view of one or more componentsassociated with at least one of the proton beam emitting system 130, thefirst proton beam delivery system 140, and the second proton beamdelivery system 142. The component status presentation 1130 canadvantageously present an intuitive and near-real-time component-levelpresentation directly obtained from interconnects for one or moreinterconnects to one or more of the proton beam delivery system 130, thefirst proton beam delivery system 140, and the second proton beamdelivery system 142. The component status presentation 1130 may includeat least one of an interlock status presentation 1132, an operatingstatus presentation 1134, and a component state presentation 1136.

The interlock status presentation 1132 includes a portion of thegraphical user interface 1100 presenting at least one operating stateidentifier associated with at least one interlock of the proton beamemitting system 130, the first proton beam delivery system 140, and thesecond proton beam delivery system 142. As one example, the interlockstatus presentation 1132 can present an operational state indicatorwhere a component included in the interlock is in a fault state. Theoperating status presentation 1134 includes a portion of the graphicaluser interface 1100 presenting at least one operating state identifierassociated with at least one interlock of the proton beam emittingsystem 130, the first proton beam delivery system 140, and the secondproton beam delivery system 142. As one example, the interlock statuspresentation 1132 can present an operational state indicator where afault state component does not cascade to an interlock fault state. Asanother example, the interlock status presentation 1132 can present afault state indicator where a fault state component does cascade to aninterlock fault state. Thus, the interlock status presentation 1132 andthe operating status presentation 1134 can together indicate whether acomponent is in a fault state and whether the component in the faultstate results in a fault state of the interlock. The component statepresentation 1136 includes a portion of the graphical user interface1100 presenting at least one operating state identifier associated withat least one component of the proton beam emitting system 130, the firstproton beam delivery system 140, and the second proton beam deliverysystem 142. The component status presentation 1130 may present a flat ornon-hierarchical list view of one or more components associated with atleast one of the proton beam emitting system 130, the first proton beamdelivery system 140, and the second proton beam delivery system 142.

FIG. 12 illustrates an example method of remote monitoring of a protonbeam emitting and delivery system, in accordance with presentimplementations. At least one of the example system 100 and thediagnostic system 600 may perform method 1200 according to presentimplementations. In some implementations, the method 1200 begins at step1210.

At step 1210, the example system obtains one or more operating statescorresponding to one or more components of a particle system. Step 1210may include step 1212. At step 1212, the example system obtains one ormore operating states from one or more components located at a remotephysical site. The method 1200 then continues to step 1220.

At step 1220, the example system associates one or more operating stateswith one or more corresponding operating indicators. The method 1200then continues to step 1230.

At step 1230, the example system generates a component hierarchycorresponding to one or more components of the particle system. Step1230 may include at least one of steps 1230 and 1232. At step 1232, theexample system generates a component hierarchy corresponding to aphysical arrangement of components of a particle system. At step 1234,the example system generates the component hierarchy including one ormore corresponding operating indicators. The method 1200 then continuesto step 1240.

At step 1240, the example system obtains at least one system interlocktemplate associated with one or more of the components of the particlesystem. Step 1240 may include step 1242. At step 1242, the examplesystem obtains at least one system interlock template including one ormore fault tolerance criterion or criteria associated with one or morecorresponding components of the particle system. The method 1200 thencontinues to step 1250.

At step 1250, the example system identifies at least one faultedphysical component from among the components of the particle system.Step 1250 may include at least one of steps 1252 and 1254. At step 1252,the example system identifies at least one device corresponding to thefaulted physical component. At step 1254, the example system identifiesa device corresponding to the faulted physical component based on atleast one fault tolerance criterion associated with the device. Themethod 1200 then continues to step 1302.

FIG. 13 illustrates an example method of remote monitoring of a protonbeam emitting and delivery system further to the example method of FIG.12. At least one of the example system 100 and the diagnostic system 600may perform method 1300 according to present implementations. The method1300 may begin at step 1302. The method 1300 then continues to step1310.

At step 1310, the example system identifies one or more fault pathcomponent among the components of the particle system. Step 1310 mayinclude step 1312. At step 1312, the example system identifies one ormore fault path components within a portion of a physical arrangement ofone or more devices or components of the particle system. The method1300 then continues to step 1320.

At step 1320, the example system modifies one or more operatingindicators corresponding to one more fault path components. Step 1320may include step 1322. At step 1322, the example system modifies one ormore operating indicators to a fault state indicator. The method 1300then continues to step 1330.

At step 1330, the example system determines whether a hierarchical or aschematic presentation type is selected. In accordance with adetermination that a hierarchical presentation type is selected, themethod 1300 continues to step 1340. In accordance with a determinationthat a schematic presentation type is selected, the method 1300continues to step 1402. The example system can determine whether ahierarchical or a schematic presentation type is selected with respectto at least a portion of a presentation at a display. The example systemcan determine to present a hierarchical presentation at a first portionof a presentation and a schematic presentation at a second portion ofthe presentation concurrently, simultaneously, independently, or thelike.

At step 1340, the example system generates a hierarchical presentation.Step 1340 may include at least one of steps 1342 and 1344. At step 1342,the example system generates a hierarchical presentation correspondingto a physical arrangement of one or more devices or components of aparticle system. At step 1344, the example system generates ahierarchical presentation including at least one faulted physicalcomponents. The method 1300 then continues to step 1350.

At step 1350, the example system traverses a hierarchical presentation.Step 1350 may include step 1352. At step 1352, the example systemtraverses a hierarchical presentation to identify one or more fault pathcomponents. The method 1300 then continues to step 1404.

FIG. 14 illustrates an example remote monitoring of a proton beamemitting and delivery system further to the example method of FIG. 13.At least one of the example system 100 and the diagnostic system 600 mayperform method 1400 according to present implementations. In someimplementations, the method 1400 begins at step 1402. The method 1400then continues to step 1410.

At step 1410, the example system generates at least one schematicpresentation. Step 1410 may include at least one of steps 1412 and 1414.At step 1412, the example system generates at least one schematicpresentation including one or more components operatively coupled to atleast one faulted physical component. At step 141, the example systemgenerates at least one schematic presentation including one or morefault path components operatively coupled to at least one faultedphysical component. The method 1400 then continues to step 1420.

At step 1420, the example system determines whether a user presentationtype corresponds to a technician presentation or a clinicianpresentation. In accordance with a determination that a userpresentation type corresponds to a technician presentation, the method1400 continues to step 1430. Alternatively, in accordance with adetermination that a user presentation type corresponds to a clinicianpresentation, the method 1400 continues to step 1440.

At step 1430, the example system authorizes a fault monitor presentationincluding presentation of one or more components of a particle system inone or more of a hierarchical presentation and a schematic presentation.The method 1400 then continues to step 1440.

At step 1440, the example system presents at least one of a hierarchicalfault monitor presentation and a schematic fault monitor presentation.Step 1440 may include at least one of steps 1442 and 1444. At step 1442,the example system presents at least one fault monitor presentationincluding one or more operating indicators. At step 1444, the examplesystem presents at least one fault monitor presentation including atleast one faulted component presentation portion. The method 1400 mayend at step 1440.

FIG. 15 illustrates an example method of remote control of a proton beamemitting and delivery system, in accordance with presentimplementations. At least one of the example system 100 and thediagnostic system 600 may perform method 1500 according to presentimplementations. The method 1500 may begin at step 1510.

At step 1510, the example system generates one or more operating stateindicators corresponding to one or more operating states associated withone or more corresponding components of a particle system. The method1500 then continues to step 1520.

At step 1520, the example system presents at least one fault controlinterface including at least one control affordance. Step 1520 mayinclude at least one of steps 1522 and 1524. At step 1522, the examplesystem presents at least one control affordance corresponding to atleast one component of a particle system. At step 1524, the examplesystem presents at least one fault control interface including at leastone corresponding faulted component presentation portion. The method1500 then continues to step 1530.

At step 1530, the example system presents at least one arrangementpresentation including one or more components. Step 1530 may include atleast one of steps 1532, 1534 and 1536. At step 1532, the example systempresents at least one arrangement presentation including at least oneinterlock associated with one or more components of the particle system.At step 1534, the example system presents at least one arrangementpresentation including at least one operating state indicatorcorresponding to one or more components of the particle system. At step1536, the example system presents at least one arrangement presentationincluding at least one operating state indicator corresponding to atleast one interlock corresponding to one or more components of theparticle system. The method 1500 then continues to step 1540.

At step 1540, the example system polls for at least one controlauthorization instruction. Step 1540 may include step 1542. At step1542, the example system polls a remote clinical site for at least onecontrol authorization instruction. The method 1500 then continues tostep 1550.

At step 1550, the example system receives at least one controlaffordance activation indication. The method 1500 then continues to step1560.

At step 1560, the example system generates at least one device commandcorresponding to at least one component corresponding to a controlaffordance. The method 1500 then continues to step 1602.

FIG. 16 illustrates an example method of remote control of a proton beamemitting and delivery system further to the example method of FIG. 15.At least one of the example system 100 and the diagnostic system 600 mayperform method 1600 according to present implementations. The method1600 may begin at step 1602. The method 1600 then continues to step1610.

At step 1610, the example system determines whether a controlauthorization instruction is received before a control affordanceactivation instruction is received. In accordance with a determinationthat a control authorization instruction is received before a controlaffordance activation instruction is received, the method 1600 continuesto step 1620. Alternatively, in accordance with a determination that acontrol authorization instruction is not received before a controlaffordance activation instruction is received, the method 1600 continuesto step 1660.

At step 1620, the example system transmits at least one device commandto at least one corresponding component. Step 1620 may include at leastone of steps 1622 and 1624. At step 1622, the example system transmitsat least one device command by at least one interconnect correspondingto the component. At step 1624, the example system transmits at leastone device command to modify at least one operating state correspondingto the component. The method 1600 then continues to step 1630.

At step 1630, the example system modifies at least one controlaffordance. The example system may modify the control affordance inresponse to a user interaction to execute an operation by the controlaffordance. The method 1600 then continues to step 1640.

At step 1640, the example system modifies at least one operating stateindicator. In some implementations, the example system modifies at leastone operating state indicator corresponding to a component of theparticle system. The method 1600 then continues to step 1650.

At step 1650, the example system presents at least one modified faultstate control interface. Step 1650 may include at least one of steps1652 and 1654. At step 1652, the example system presents at least onemodified control affordance corresponding to the component associatedwith the modified operating state indicator. At step 1654, the examplesystem presents one or more modified operating state indicatorscorresponding to the modified control affordance. The method 1600 thencontinues to step 1660.

At step 1660, the example system blocks transmitting of at least onedevice command to at least one component corresponding to the devicecommand. The method 1600 may end at step 1660.

FIG. 17 illustrates an example method of remote control of a proton beamemitting and delivery system at a service location, in accordance withpresent implementations. At least one of the example system 100 and thediagnostic system 600 may perform method 1700 according to presentimplementations. The method 1700 may begin at step 1710.

At step 1710, the example system obtains at least one detection of atleast one component at a clinical site. A site can be a particularphysical location or collection of physical locations. Step 1710 mayinclude at least one of steps 1712, 1714 and 1716. At step 1712, theexample system obtains at least one detection at a technician siteremote from the clinical site. At step 1714, the example system obtainsat least one detection from at least one component of a proton emittingsystem. At step 1716, the example system obtains at least one detectionfrom at least one component of a proton delivery system. The method 1700then continues to step 1720.

At step 1720, the example system identifies at least one deviceincluding at least one component at the clinical site. A device can beor correspond to an interlock associated with the group. Step 1720 mayinclude at least one of steps 1722 and 1724. At step 1722, the examplesystem identifies one or more devices of the proton emitting system. Atstep 1724, the example system identifies one or more devices of theproton delivery system. The method 1700 then continues to step 1730.

At step 1730, the example system associates at least one interlockoperating state with at least one corresponding device. Step 1730 mayinclude at least one of steps 1732 and 1734. At step 1732, the examplesystem associates at least one interlock operating state with at leastone corresponding device by at least one operating state associated withat least one of the components. At step 1734, the example systemassociates at least one interlock operating state with at least onecorresponding device by at least one interlock condition associated withat least one of the components. The method 1700 then continues to step1802.

FIG. 18 illustrates an example method of remote control of a proton beamemitting and delivery system at a service location, further to theexample method of FIG. 17. At least one of the example system 100 andthe diagnostic system 600 may perform method 1800 according to presentimplementations. The method 1800 may begin at step 1802. The method 1800then continues to step 1810.

At step 1810, the example system monitors at least one operating stateassociated with at least one component at the technician site. Step 1810may include at least one of steps 18112 and 1814. At step 1812, theexample system monitors one or more components of a proton emittingsystem. At step 1814, the example system monitors one or more componentsof a proton delivery system. The method 1800 then continues to step1820.

At step 1820, the example system transmits one or more modifiedoperating states corresponding to one or more components. Step 1820 mayinclude at least one of steps 1822 and 1824. At step 1822, the examplesystem transmits one or more modified operating states to one or morecorresponding components of a proton emitting system. At step 1824, theexample system transmits one or more modified operating states to one ormore corresponding components of a proton delivery system. The method1800 may end at step 1820.

FIG. 19 illustrates an example method of remote control of a proton beamemitting and delivery system at a clinical location, in accordance withpresent implementations. At least one of the example system 100 and theproton beam system gateway 200 may perform method 1900 according topresent implementations. The method 1900 may begin at step 1910.

At step 1910, the example system initializes one or more components at aclinical site. Step 1910 may include at least one of steps 1912, 1914and 1916. At step 1912, the example system initializes one or morecomponents of a proton beam emitting system. At step 1914, the examplesystem one or more components of a proton beam delivery system. At step1916, the example system initializes one or more components of a protonbeam gateway system. The method 1900 then continues to step 1920.

At step 1920, the example system detects one or components at a clinicalsite. In some implementations, step 1920 includes at least one of steps1922, 1924 and 1926. At step 1922, the example system detects one orcomponents at a clinical site remote from a technician site. At step1924, the example system detects one or components of a proton beamemitting system. At step 1926, the example system detects one orcomponents of a proton beam delivery system. The method 1900 thencontinues to step 1930.

At step 1930, the example system interrogates one or more components forone or more corresponding operating states associated with thecomponents. In some implementations, step 1930 includes at least one ofsteps 1932 and 1934. At step 1932, the example system interrogates oneor more components corresponding to one or more components of a protonbeam emitting system. At step 1934, the example system interrogates oneor more components corresponding to one or more components of a protonbeam emitting system. The method 1900 then continues to step 2002.

FIG. 20 illustrates an example method of remote control of a proton beamemitting and delivery system at a clinical location, further to theexample method of FIG. 19. At least one of the example system 100 andthe proton beam system gateway 200 may perform method 2000 according topresent implementations. The method 2000 may begin at step 2002. Themethod 2000 then continues to step 2010.

At step 2010, the example system transmits one or more operating statesto a technician site. Step 2010 may include at least one of steps 2012and 2014. At step 2012, the example system transmits one or moreoperating states associated with a proton emitting system. At step 2014,the example system transmits one or more operating states associatedwith a proton delivery system. The method 2000 then continues to step2020.

At step 2020, the example system receives one or more modified operatingstates for one or more components. Step 2020 may include at least one ofsteps 2022 and 2024. At step 2022, the example system receives one ormore modified operating states at one or more components of a protonemitting system. At step 2024, the example system receives one or moremodified operating states at one or more components of a proton deliverysystem. The method 2000 then continues to step 2030.

At step 2030, the example system modifies one or more operating statesfor one or more components at a clinical site. Step 2030 may include atleast one of steps 2032 and 2034. At step 2032, the example systemmodifies one or more component of a proton emitting system. At step2034, the example system modifies one or more component of a protonemitting system. In some implementations, the method 2000 ends at step2030.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures areillustrative, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected,” or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

With respect to the use of plural and/or singular terms herein, thosehaving skill in the art can translate from the plural to the singularand/or from the singular to the plural as is appropriate to the contextand/or application. The various singular/plural permutations may beexpressly set forth herein for sake of clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.).

Although the figures and description may illustrate a specific order ofmethod steps, the order of such steps may differ from what is depictedand described, unless specified differently above. Also, two or moresteps may be performed concurrently or with partial concurrence, unlessspecified differently above. Such variation may depend, for example, onthe software and hardware systems chosen and on designer choice. Allsuch variations are within the scope of the disclosure. Likewise,software implementations of the described methods could be accomplishedwith standard programming techniques with rule-based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps, and decision steps.

It will be further understood by those within the art that if a specificnumber of an introduced claim recitation is intended, such an intentwill be explicitly recited in the claim, and in the absence of suchrecitation, no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations).

Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general,such a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.”

Further, unless otherwise noted, the use of the words “approximate,”“about,” “around,” “substantially,” etc., mean plus or minus tenpercent.

The foregoing description of illustrative implementations has beenpresented for purposes of illustration and of description. It is notintended to be exhaustive or limiting with respect to the precise formdisclosed, and modifications and variations are possible in light of theabove teachings or may be acquired from practice of the disclosedimplementations. It is intended that the scope of the invention bedefined by the claims appended hereto and their equivalents.

What is claimed is:
 1. A system for remote diagnostic monitoring andcontrol of physical components of a particle accelerator system, thesystem comprising: a particle emitting system located at a firstphysical site and including one or more particle emitting systemcomponents to operate the particle emitting system; a particle deliverysystem located at the first physical site and including one or moreparticle delivery system components to operate the particle deliverysystem; a particle system gateway located at the first physical site andoperatively coupled to the particle emitting system components and theparticle delivery system components by a first network interface; and adiagnostic monitoring system located at a second physical site remotefrom the first physical site, operatively coupled to the particle systemgateway by a second network interface, and operable to monitor one ormore first operating states corresponding to one or more of the particleemitting system components and one or more second operating statescorresponding to one or more of the particle delivery system components;and a diagnostic control system located at the second physical site,operatively coupled to the particle system gateway by a third networkinterface, and operable to modify one or more of the first operatingstates of the one or more particle emitting system components and thesecond operating states the one or more particle delivery systemcomponents.
 2. The system of claim 1, wherein the particle systemgateway further comprises: a component detector configured to perform acomponent detection operation to detect one or more of the particleemitting system components present at the particle emitting system andone or more of the particle delivery system components present at theparticle delivery system.
 3. The system of claim 2, wherein thecomponent detector is further configured to perform the componentdetection operation during initialization of one or more of the particlesystem gateway, the particle emitting system, and the particle deliverysystem.
 4. The system of claim 2, wherein the component detector isfurther configured to perform the component detection operation byinterrogating one or more of the particle emitting system components andone or more of the particle delivery system components.
 5. The system ofclaim 1, wherein the particle system gateway further comprises: aninterlock processor configured to perform a component dependencyoperation to identify at least one particle system device including atleast one included particle system component, wherein the particlesystem component includes at least one of the particle emitting systemcomponents present at the particle emitting system, or at least one ofthe particle delivery system components present at the particle deliverysystem.
 6. The system of claim 5, wherein the diagnostic control systemfurther comprises: an interlock controller configured to perform acomponent interlock operation to associate an interlock operating statewith the particle system device, the interlock state based on acomponent operating state of the particle system component and aninterlock condition, wherein the component operating state correspondsto at least one of the first operating states and the second operatingstates.
 7. The system of claim 6, wherein the interlock conditioncomprises an instruction to modify the device operating state tocorrespond to the component operating state.
 8. The system of claim 7,wherein the device operating state and the component operating statecomprise a fault state.
 9. The system of claim 1, further comprising: asecond particle delivery system located at the first physical site andincluding one or more second particle delivery system components tooperate the second particle delivery system independently of the firstparticle delivery system, wherein the particle system gateway is furtheroperatively coupled to the second particle delivery system components bythe first network interface.
 10. The system of claim 2, wherein thediagnostic monitoring system is further operable to monitor one or morethird operating states corresponding to one or more of the secondparticle emitting system components, and the diagnostic control systemis further operable to modify one or more of the third operating states.11. A method for remote diagnostic monitoring and control of physicalcomponents of a particle accelerator system, the method comprising:obtaining, by at least one processor at a second physical site, from aparticle system gateway located at a first physical site, a detection ofone or more particle emitting system components present at a particleemitting system located at the first physical site and including one ormore of the particle emitting system components to operate the particleemitting system; obtaining, by the at least one processor, from theparticle system gateway, a detection of one or more particle deliverysystem components present at a particle delivery system located at thefirst physical site and including one or more of the particle deliverysystem components to operate the particle delivery system; monitoring,by the at least one processor, one or more first operating statescorresponding to one or more of the particle emitting system componentsand one or more second operating states corresponding to one or more ofthe particle delivery system components; and transmitting, by the atleast one processor, one or more of one or more first modified operatingstates based on one or more of the first operating states of the one ormore particle emitting system components, and one or more secondmodified operating states based on one or more of the second operatingstates of the one or more particle delivery system components.
 12. Themethod of claim 11, further comprising: identifying, by the at least oneprocessor, at least one particle system device including at least oneincluded particle system component, wherein the particle systemcomponent includes at least one of the particle emitting systemcomponents present at the particle emitting system, or at least one ofthe particle delivery system components present at the particle deliverysystem.
 13. The method of claim 12, further comprising: associating, bythe at least one processor, an interlock operating state with theparticle system device, wherein the interlock state is based on acomponent operating state of the particle system component and aninterlock condition, and the component operating state corresponds to atleast one of the first operating states and the second operating states.14. The method of claim 13, wherein the interlock condition comprises aninstruction to modify the device operating state to correspond to thecomponent operating state.
 15. The method of claim 11, wherein theparticle system gateway is operatively coupled to the particle emittingsystem components and the particle delivery system components by a firstnetwork interface.
 16. The method of claim 15, wherein the diagnosticmonitoring system is located at a second physical site remote from thefirst physical site, and is operatively coupled to the particle systemgateway by a second network interface.
 17. The method of claim 16,wherein the diagnostic control system is located at the second physicalsite, and is operatively coupled to the particle system gateway by athird network interface.
 18. A method for remote diagnostic monitoringand control of physical components of a particle accelerator system, themethod comprising: detecting, by a particle system gateway located at afirst physical site, one or more particle emitting system componentspresent at a particle emitting system located at the first physical siteand including one or more of the particle emitting system components tooperate the particle emitting system; detecting, from the particlesystem gateway, one or more particle delivery system components presentat a particle delivery system located at the first physical site andincluding one or more of the particle delivery system components tooperate the particle delivery system; transmitting, to a diagnosticmonitoring system located at a second physical site remote from thefirst physical site, one or more first operating states corresponding toone or more of the particle emitting system components and one or moresecond operating states corresponding to one or more of the particledelivery system components; and receiving, from a diagnostic controlsystem located at the second physical site, one or more of firstmodified operating states of the one or more particle emitting systemcomponents and second modified operating states of the one or moreparticle delivery system components.
 19. The method of claim 18, furthercomprising: initializing one or more of the particle system gateway, theparticle emitting system, and the particle delivery system, wherein thedetecting the particle emitting system components comprises detectingthe particle emitting system components present at the particle emittingsystem, in response to the initializing, and the detecting the particledelivery system components comprises detecting the particle deliverysystem components present at the particle delivery system, in responseto the initializing.
 20. The system of claim 18, further comprising:interrogating one or more of the particle emitting system components andone or more of the particle delivery system components.